FiraDisk, File/RAM Disk driver for Windows. External links Rating Options

[karyonix]

@jaclaz
I just wrote the first thing I can think of. Using sc command should be better than editing registry manually.

@joakim
1. I have tested it for a short time with few reboots. If someone want to use it longer than that, it is a good idea to do as you suggested.
2. I don't have VistaPE, so I don't know. Can you add entries in its Enum registry key like you do for XP PE?

[joakim]

@joakim
2. I don't have VistaPE, so I don't know. Can you add entries in its Enum registry key like you do for XP PE?

Yes, the system.hiv has replaced setupreg.hiv. But since parts of txtsetup.sif has moved into the bcd store, it is not as easy to force load drivers as it was. You probably have to tweak the ramdiskoptions and replace boot.sdi with something. I have tried many different things earlier, but got stuck and came nowhere. If you have some great theories, I'm interested.

Joakim

[oriensol]

@joakim

Have you got this to work in Livexp? I am able to see the SCSI & Raid Controller Firadisk Driver in Livexp but the disk itself is not recognised.

[joakim]

@joakim
Have you got this to work in Livexp? I am able to see the SCSI & Raid Controller Firadisk Driver in Livexp but the disk itself is not recognised.

I am not the most experienced livexp user here and have not tried firadisk with livexp.

I have earlier experienced problems with livexp detecting certain storage. I am going to do more ramloading tests in the near future and livexp-related will be one of them.

Joakim

[oriensol]

@joakim

Ok thanks. I am trying to make the Livexp work and will post the script if I succeed.

oriensol

[fujianabc]

Here is the txtsetup.oem for firadisk, in which x86 is the default. It can be used in an F6 floppy.

CODE

[Disks]
d1 = "FiraDisk Installation Disk", \firadisk.sys, \
d1 = "FiraDisk Installation Disk", \firadisk64.sys, \

[Defaults]
scsi = firadisk32

[scsi]
firadisk32 = "FiraDisk Virtual Disk Driver x86",firadisk
firadisk64 = "FiraDisk Virtual Disk Driver x64",firadisk

[Files.scsi.firadisk32]
driver     = d1,firadisk.sys,firadisk
inf        = d1,firadisk.inf

[Files.scsi.firadisk64]
driver     = d1,firadisk64.sys,firadisk
inf        = d1,firadisk.inf

[cdob]

@fujianabc

How do you use this txtsetup.oem?
Do you use a real floppy drive?
Do you use a virtual floppy at a virtual machine?
Do you have a example?

I tried a grub4dos virtual floppy drive.

menu.lst

CODE

title winnt.sif virtual floppy (fd0) and boot SETUPLDR.BIN
map --mem /I386/WINNTSIF.IMA (fd0)
map --hook
chainloader /I386/SETUPLDR.BIN

txtsetup.oem

CODE

[Disks]
disk1 = "VMware SCSI Controller Installation Disk", \disk.tag, \

[Defaults]
scsi = VMSCSI

[scsi]
firadisk = "FiraDisk Virtual Disk Driver"
VMSCSI = "VMware SCSI Controller"


[Files.scsi.firadisk]
driver = disk1, firadisk.sys,firadisk
inf = disk1, firadisk.inf


[Files.scsi.VMSCSI]
driver = disk1, vmscsi.sys, VMSCSI
inf = disk1, vmscsi.inf
catalog = disk1, vmscsi.cat

;driver = disk1, FiraDisk.sys, firadisk
;inf = disk1, firadisk.inf


[Config.VMSCSI]
# Add registry value
# HKLM\System\CurrentControlSet\VMSCSI\Tag with value of 5
value = "", Tag, REG_DWORD, 5

# HKLM\System\CurrentControlSet\VMSCSI\Parameters\PnPInterface\5
# The subkey name should be 5 for PCIBus
# The value of the subkey should be 1 for PnP enabled or 0 for disabled.
value = Parameters\PnpInterface, 5 ,REG_DWORD, 1

# set max outstanding requests to the adapter
value = Parameters\Device, NumberOfRequests, REG_DWORD, 128

[HardwareIds.scsi.VMSCSI]
id = "PCI\VEN_104B&DEV_1040", "VMscsi"

The floppy (fd0) is mapped to C: \Device\Harddisk1\Partition1
Setup dosn't find this drive for file copy.

[joakim]

There appears to be something wrong with the last version, as I get BSOD 7B on both livexp and moa (2k3sp2 sources) when booting off diskimage with "map --mem".

It is the same setup that worked with moa with the first version. Patching the same image back to first version of driver boots fine though.

What happened to last version?

Joakim

[fujianabc]

@fujianabc

How do you use this txtsetup.oem?
Do you use a real floppy drive?
Do you use a virtual floppy at a virtual machine?
Do you have a example?

The txtsetup.oem is used to load firadisk driver if you want to setup xp/2003 from iso or boot from a winpe iso.
In the floppy, it should contain txtsetup.oem, firadisk.inf,firadisk.sys

To start setup from winxp.iso

CODE

title start xp setup from iso
map --mem (hdx,x)/Firadisk.vfd (fd1)
map --mem (md)0x6000+800 (fd0)
map --mem (hdx,x)/winxp.iso (0xff)
map --hook
dd if=(fd1) of=(fd0) count=1
chainloader (0xff)

And windows setup can load firadisk drive from (fd1) and install the driver to winxp automatically, and you needn't press F6.

CODE

title boot pe 1.x from iso
map --mem (hdx,x)/Firadisk.vfd (fd0)
map --mem (hdx,x)/xpe.iso (0xff)
map --hook
chainloader (0xff)

setupldr.bin can load Firadisk driver from fd0 for winpe automatically, and you still needn't press F6.

[cdob]

The txtsetup.oem is used to load firadisk driver if you want to setup xp/2003 from iso or boot from a winpe iso.
In the floppy, it should contain txtsetup.oem, firadisk.inf,firadisk.sys

Thanks, that's nice.
My old BartPE.iso does contain a winnt.sif with [massstoragedrivers].
Firadisk was not found, searched at \$OEM$\firadisk

Did add winnt.sif to the floppy image, almost empty, one line only

[Data]

Awesome RAM loaded booting a old existing PE image.

To start setup from winxp.iso

That's clever grub4dos usage.