630 replies to this topic

[karyonix]

Another question, can we include your driver inside the script?

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.

[oriensol]

@karyonix

Thanks for the detailed post. I understand you do not mind if your driver is included in the script. I think I will follow the advice of the experts here on how to include the driver.

I have entries for HardwareIdsDatabase in the registry and also in txtsetup.sif. The service is also up when Livexp boots:

X:\>sc query firadisk

	   SERVICE_NAME		 : firadisk

	   TYPE					  : 1  KERNEL_DRIVER

	   STATE					: RUNNING

									(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)

	   WIN32_EXIT_CODE	: 0  (0x0)

	   SERVICE_EXIT_CODE : 0  (0x0)

	   CHECKPOINT			: 0x0

	   WAIT_HINT			  : 0x0

X:\>

So we should be fine, I assume. (This is with 0.0.1.10 and 2k3 source).

[oriensol]

@joakim

Quick update. I am sorry I seem to have tested the wk2r3 part with the wrong iso. Am getting BSOD 7B when I retested carefully.

Will keep you updated. Sorry.

[karyonix]

Bug v0.0.1.10
Cannot read hexadecimal number from boot option.
If you use firadisk boot option with v0.0.1.10, use only decimal number.

[led9]

karyonix

I have 8 Gb RAM
win32.img Makes ~3 Gb
Win32 From win32.img boots normally (thanks!
After loading of free memory remains only 204 mbytes

How an image win32 to load into not used memory (> 3.2 Gb)?
and boot from "not used" memory?

[karyonix]

@led9
GRUB4DOS 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, joakim
WS2003's problem is in classpnp as described here. http://www.techtalkz...r-2003-sp1.html
Calculated 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.

[oriensol]

@karyonix

Glad to say with the new version 0.0.1.12 - booting from Firadisk mapped Livexp iso works great, with Win2k3 sources.

[was_jaclaz]

...
I have 8 Gb RAM
win32.img Makes ~3 Gb
Win32 From win32.img boots normally (thanks!
...

Out of curiosity, how long does it take to boot such a huge image?

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).

jaclaz

[karyonix]

Test with Windows 7 RC 32-bit

map --mem (hd0,0)/hddimg.img (hd3)
map --mem (hd2,1)/devel/testdata/cdimg.iso (hd32)
root (hd0,0)
chainloader /bootmgr

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Win7 with RAM drive at 4G
locale en-US
loadoptions firadisk=disk,physicalmemory,offset=0x100000000,size=0x30000000
inherit {bootloadersettings}
recoverysequence {571861b2-9a4e-11de-ba7d-e22c7dbad191}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {571861b0-9a4e-11de-ba7d-e22c7dbad191}
nx OptIn

- RAM Disk loaded with map --mem : Works
- RAM CD-ROM loaded with map --mem : This device cannot start. (Code 10)
- RAM Disk create with boot option : Appear uninitialized in Disk Management. Can be initialized, partitioned, formatted.

It seems virtual CD-ROM Drive is still not good in Win7RC.

[oriensol]

Here's the Livexp update:

Tested the following:

With XP sources (versions 0.0.1.10 and 0.0.1.12) :
1. Booting Livexp from a Firadisk Livexp Iso (menu.lst):

title LiveXP-Firadisk

map --mem (hd1,0)/test_img.img (hd3)

map --mem (hd1,0)/pmagic-4.3.iso (hd32)

map --mem (hd1,0)/minlex/ISO/LiveXP.iso (0xFF)

map --hook

chainloader (0xFF)

2. Booting Livexp from cd with non-boot Firadisk defined using grub4dos.
3. Booting firadisk LiveXP.iso over network using tftpboot/grub4dos.

With Win2k3 sources (version 0.0.1.12):
1. Booting Livexp from a Firadisk Livexp Iso

Will upload the script in the other thread: http://www.boot-land...?...pic=8862=

Thanks.

[led9]

I cannot load windows xp 64 bit from memory.
Tested
windows xp 64 bit sp1
windows xp 64 bit sp2

firadisk-driver-0.0.1.10
firadisk-driver-0.0.1.12

The image is loaded into memory normally, there is a logo windows xp 64 bit, loading lasts certain time, the loading indicator runs, then the blue screen:

BSOD Unmountable_boot_volume

STOP 0x000000ED (0xFFFFFADF86F16840, 0xFFFFFFFFC000014F, 0,0)

What do I do not so?
(win32 to load from memory it was possible, with win64 did similarly)


jaclaz
from sata hdd less 1 min

[shuini]

hi.
My OS is 32-bit windows2003 RAMOS, FiraDisk = 0.0.1.12
technical information:
stop: 0X0000007B (0XF789EA94, 0XC0000034, 0X00000000, 0X00000000)

Thanks！

[karyonix]

@led9
Does it work for non-boot drive ?

@shuini
What is your setup detail ?
How do you install firadisk ?
How do you load image and boot when this error occurs ?
Does it work for non-boot drive ?

[shuini]

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.

In addition, RAMOS_XP successful!

Thanks

[winxp]

help,help
firadisk do boot win2003pe is fine,but load program err,booting in win2003pe not see iso cdrom?please help me!!

menu.lst

title [8] -- 用firadisk驱动启动win2003pe.iso
find --set-root /Firadisk.img
map --mem /Firadisk.img (fd0)
map --hook
find --set-root /w3pe.iso
map --mem (hd0,0)/w3pe.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)
boot

[karyonix]

@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.

[bardlet]

 HDTune_Benchmark_.png   79.15KB   99 downloads
so slowly
i believe u can make it better
Thanks a lot

[dog]

so slowly

I get similar results from winvblock on a dual 2GHz:
 hdtune.JPG   58.91KB   64 downloads

[karyonix]

It is really slow. I will find a way to improve it.
I have an idea but it will probably take several days to implement.

[led9]

karyonix
And 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

[MedEvil]

It is really slow. I will find a way to improve it.

Has anyone ever done a similar speed tests with any of the other available ramdisks?
Cause it looks average to me.

[was_jaclaz]

Has anyone ever done a similar speed tests with any of the other available ramdisks?
Cause it looks average to me.

Which should mean that you ran those tests....

(and at least two of them to be able to have an average )



jaclaz

[was_JFX]

Works great on 2k3/XP PE or full Windows

But really seems to have a problem with Win XP x64. Installes nicly with devcon (x64), but no drive there after boot.

[karyonix]

@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.

What do you think I should do first ?

[oriensol]

- 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)

@karyonix

One difference I see is that, Firadisk works with Disk Management and other partition tools, whereas if you mount using ImDisk, VDK, etc. you cannot use those tools, as far as I know.