Thread: Ramdisk
View Single Post
  #26  
Old December 30th 19, 07:56 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Ramdisk

Mayayana wrote:
"Mayayana" wrote
| "Shadow" wrote
|
|| RAMDisk.exe is actually a VB6 executable. The Microsoft Visual
|| C# / Basic.NET / MS Visual Basic 2005,7 and 10 files appear to be the
|| registration routine.
||
|
| Yes. I know it's VB6. I think we're crossing wires here.
|
| There's no .Net in Dataram's program. And the installer is
| not .Net. It's just an MSI.

I realized later that you're probably talking about the
newer Dataram Ramdisk. As I noted above, I'm using the
older version, which has no .Net and supports XP. Later
versions added .Net. Still later versions dropped XP support.
The basic functionality is actually a driver. But the GUI
uses VB6 or .Net, depending on the version. From what
I can gather, the version I have seems to be a thrown-
together VB6 GUI that mainly just existing as a front-end to
the INF file, so that the RAMDisk can be installed or
uninstalled conveniently.

My guess is that the author(s) is someone knowledgeable
about low level functionality like drivers but just grabs
what's handy for the GUI and installer. Or maybe told the
new guy to do it.


DataRAM, as a company, is a "seller of DIMMs".

The RAMDisk software product, is a sideline.

My suspicion is, the product is provided by a "contractor",
and a dedicated staff is not likely to exist in the
DataRAM building. I would not try to imagine a "quality"
department beating on a local developer, trying to make
him or her do the right thing.

And the reason you use a contractor, is ramdisks
are hard, and it's taken an inordinate amount of
time for a RAMDisk to be as capable as that one
is. If you have any experience with older RAMDisks,
the difference is night and day. The first RAMDisk
was sample code Microsoft provided, and that put people
down wrong paths for a long long time. They tried to
iterate that code, to no good effect. It's a bit
like the "AmCap effect", where the AmCap code took
an inordinate amount of time to be augmented by
a developer and beat into decent shape. In a sense,
sample code seems to do an awful lot of damage, human
nature being what it is.

Paul
Ads