[tyn]

Hi,
I need to maintain the same drive location for my RAM drive created with Starport eg. X:\

There doesn't seem to be a way to specify the mount point in the Starport interface so I change it in the WinXP disk management tool. This works for my current session but after I reboot the drive gets mounted to an automatic location. I think it is the first free drive letter.

Any help is appreciated.


Ty

[tyn]

I can see a few people have read my original query - but no replies.

Does anyone else think it is a good idea to be able to set the location of your RAM drive so it is maintained between reboots?

Actually, dumping the RAM drive to a disk file on shutdown would also be an excellent feature.

I heard Gigabyte demo'd a PCI card RAM disk at E3. Now that's an excellent idea if you ask me.


Ty

[Underheaven]

I dunno tyn, I guess this section of the board isn't monitored much by the people who work at RocketDivision. I think you want someone who programs the software to read your message. I guess they just haven't seen it yet.

You could email KOOLER with this link and ask him to visit the forum, seems he hasn't been here since January of this year. He's listed as the moderator, as I am sure you can tell.


In terms of your ideas, I think both of them are great as long as you don't expect to mount a RAM drive (during system startup) under an important or critical location like '%userprofile%\Local Settings\Temp' or '%userprofile%\Desktop' or '%systemroot%\Temp'

The Gigabyte PCI card seems interesting too, as long as its as reliable as the rest of the RAM in your system. For example, some PCI cards have problems with waking up from one of the various ACPI sleep states (S5, S4, S3, S2, S1, S0) and I'd hate to lose unsaved work because of that. But if something is going to be sold in retail stores, I'm sure bugs involving memory loss would never happen, so I'm probably concerned for no reason.

[KOOLER]

Could ge a good idea to keep memory between boots. However the problem is - StarPort is more of the "proof of concept" then a commercial product. This mean "yes, we can write monolithic SCSI port driver, nobady can do this except us and Microsoft and some other companies", "yes, we can write iSCSI initiator for Windows, nobady can except us, Microsoft, even IBM and Cisco dropped this idea", "yes, we can write CD/DVD emulator and RAM disk emulator - looking for custom work? here we are!". Such an approach works fine for us. However StarPort would be not be ever functionally complete CD/DVD emulator or RAM disk driver - it's not designed to be it and competite with Daemon Tools or whatever. It's approach to be 1) iSCSI initiator working faster with StarWind then MS iSCSI initiator and 2) other storage protocols initiator (would be released some interesting things soon).

[tyn]

Hi,
Thanks for the reply. I totally understand where your coming from... I am a software developer as well and I know that most software is never really finished and the time and effort it takes to put a quality product together is considerable.

It just seems like the solution is lacking in this area and the amount of work required to get something going should be very small. I am happy to contribute my time to writing this code if you are happy to let me participate (? temporarily ?) in your project?

What I'm talking about is: after Starport completes its usual start-up routine it looks for configuration data defining what devices to auto-mount. I was hoping it would be a simple matter of calling the same routine that is used at the end of the "add device" wizard. The GUI for setting up a device for "auto-mount at start-up" can be as simple as adding a check-box to the "add device" wizard; to remove the "auto-mount at start-up" setting use a check-box in the "device properties" dialog. Store the setting in a configuration file located in the directory where the Starport executable is being run; or, if you want to allow per-user settings, put it in the users home directory.

Anyway, the offer is open if you want to take it up.


Ty

[KOOLER]

Please drop me a message with appropriate subject to anton@rocketdivision.com and we would disuss this stuff. Thanks!

Originally Posted by tyn

Hi,
Thanks for the reply. I totally understand where your coming from... I am a software developer as well and I know that most software is never really finished and the time and effort it takes to put a quality product together is considerable.

It just seems like the solution is lacking in this area and the amount of work required to get something going should be very small. I am happy to contribute my time to writing this code if you are happy to let me participate (? temporarily ?) in your project?

What I'm talking about is: after Starport completes its usual start-up routine it looks for configuration data defining what devices to auto-mount. I was hoping it would be a simple matter of calling the same routine that is used at the end of the "add device" wizard. The GUI for setting up a device for "auto-mount at start-up" can be as simple as adding a check-box to the "add device" wizard; to remove the "auto-mount at start-up" setting use a check-box in the "device properties" dialog. Store the setting in a configuration file located in the directory where the Starport executable is being run; or, if you want to allow per-user settings, put it in the users home directory.

Anyway, the offer is open if you want to take it up.


Ty