You can. I don't known how LiveXP scripts work. I can't help in creating it.

Don't worry too much about the message in device manager that firadisk have no driver installed. It does not affect its operation. But if you can find the right registry settings, it would look good to users.

I learned about CriticalDeviceDatabase after I read Emanuel Schleussinger's article and Dietmar's thread about USB booting.Usually when you add a new plug-and-play device to computer, the device do not have driver and cannot work. However, if you have devices' HardwareID or CompatibleID in CriticalDeviceDatabase (or HardwareIdsDatabase), Windows will use service specified by service value in this key to drive the device temporarily until it have a driver installed. Legacy device detected by a driver (for example, detected\firadisk) use that driver to function temporarily until a driver is installed for that device.

If Windows find a matching driver signed by a trusted publisher, it install a driver automatically. The device is removed from temporary driver and add to newly installed driver immediately. If Windows cannot find a trusted driver, it asks user to install driver for the device. The temporary driver continue to drive the device until a matching driver is installed or computer shutdown.

It seems Windows setup during txtsetup pass and PE don't ask user to install driver. It just use (driver from database) or (the driver which report detected device) until reboot.

@led9GRUB4DOS 0.4.4 don't load data to >4GB address. If you can change GRUB4DOS to create RAM drive there, FiraDisk can use it.

@oriensol, joakimWS2003's problem is in classpnp as described here. http://www.techtalkz...r-2003-sp1.htmlCalculated from IoAllocateMdl documentation + DDK header file, maximum number of pages an MDL can describe is 16376 for 32-bit Windows and 8185 for 64-bit Windows.I have adjusted MaximumPhysicalPages value in new version of FiraDisk accordingly.

Here is new version v0.0.1.12.http://www.mediafire...er-0.0.1.12.zip- Fix hexadecimal problem in boot option. Most of you don't use it though. - Attempt to fix compatibility issue with Windows Server 2003.

Wouldn't it be advisable, besides fixing the (current) grub4dos limit karyonix pointed out, to split the image in a "core" small and fast loading/booting and a "secondary" image that you can connect during booting through a "filedisk" type of driver (that won't use memory)?

If this "core" image is NTFS you can use a Mountpoint allright, you won't even know in normal operation that you have actually 2 drives (firadisk+VDK - or another one).

Sorry, my English is not good, I hope you can understand.
1. Right-click firadisk.inf, restart after the installation is complete.
2. Scrollbar appears, the blue screen.
3. RAMOS2003.img in the C:, C: is the boot disk.

@shuini
I don't know much about your RAMOS2003.
If it is similar to LiveXP, you can try looking at oriensol's script in his thread and see how he install it in his LiveXP.

@winxp
If you have floppy image and iso image in same partition, you don't have to "find --setroot" multiple times.
I don't known what is inside w3pe.iso. If it is similar to LiveXP, you can chainloader /I386/SETUPLDR.BIN directly.
find --set-root /Firadisk.img
map --mem /Firadisk.img (fd0)
map --mem /w3pe.iso (hd32) << No (hd0,0) here if file is in current root device which may not be (hd0,0).
map --hook << One should be enough
root (hd32)
chainloader /I386/SETUPLDR.BIN << Load SETUPLDR
I don't know this will help or not.

karyonixAnd you can install at yourselves winxp 64 bit and boot it from ram?Winxp64 It is the unique 64 bit version which allows to establish not signed the driver. Very much it would be desirable to involve all 8 Gb RAM

@led9
I cannot test Windows XP x64.
Today, I have just buy more RAM. Now, my PC have 8GB RAM. I may try Windows 7 RC x64 RAM drive if I can reduce Windows to below 3GB. I have no way to load disk image to above 4GB address now. RAM drive will be in lower 3.25GB RAM, leaving RAM above 4GB address for Windows' use.
----------

To do list:
- Console/GUI interface to mount/unmount image file without restarting Windows.
Not very important because other free programs that can do this already exists. (ImDisk, VDK)
- Installer
Not very important. Add Hardware Wizard is good enough.
- Study assembly and PAE and write assembly code for accessing to RAM above 4GB preboot.
It will take a long time.
- Improve speed of RAM drive
?
- Boot from image file without RAM drive.
Not possible with current FiraDisk. Require rewriting of much of the code.