Jump to content











Photo
* * * * * 7 votes

FiraDisk (latest = 0.0.1.30)


  • Please log in to reply
624 replies to this topic

#201 corsair

corsair
  • Members
  • 3 posts
  •  
    United States

Posted 01 December 2009 - 06:57 PM

Tested it works via HDtach utility!
before it was hovering around 30MB/s
now its around 1669MB/s see pic

Great job!

Attached Files



#202 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 01 December 2009 - 07:04 PM

Tested it works via HDtach utility!
before it was hovering around 30MB/s
now its around 1669MB/s see pic

Great job!



v0.0.1.16 : RAM Disk speed improvement
Enabling cache and using __movsq or __movsd instead of RtlCopyMemory result in faster transfer speed than previous versions.


I guess karyonix loves understatements! :clap:

:clap:

jaclaz

#203 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 472 posts
  •  
    Thailand

Posted 08 December 2009 - 06:23 AM

Do not get speed improvements with the new driver. It was 1:16, and left.
What is not correct.

Please include more detail such as machine spec, Windows version/edition, normal Windows or PE, how you measure its speed, and the speed you measured from old vs new versions.

Old versions have slow transfer speed problem discovered by siro. It affects only real machine but not VirtualBox, QEMU.
http://www.boot-land...?...ost&p=78256
It symptoms are slow copying of large files, slow measured read/write speed in benchmark programs.
This problem is fixed in new version. New version does not make computer run faster.

#204 kDn

kDn

    Member

  • Members
  • 58 posts
  •  
    Ukraine

Posted 08 December 2009 - 01:47 PM

Hello.

I'm using loading firadisk driver via TXTSETUP.OEM file (hidden F6 load) from grub4dos virtual FDD. Something like that:

title ERD Commander 2007.iso

map --mem /boot/_ima/firadisk.gz (fd0)

map --mem /boot/_iso/ERD50.iso (0xFF)

map --hook

chainloader (0xFF)

[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,firadk64.sys,firadisk

inf		= d1,firadisk.inf


Version 0.0.1.12 worked without any problem, but I can't modify TXTSETUP.OEM for 0.0.1.16 or simple rename FIRADISK32.SYS to FIRADISK.SYS. All variants give me BSOD 0x000000ED: UNMOUNTABLE_BOOT_VOLUME

My current TXTSETUP.OEM:

[Disks]

d1 = "FiraDisk Installation Disk", \firadk32.sys, \

d1 = "FiraDisk Installation Disk", \firadk64.sys, \



[Defaults]

scsi = firadisk32



[scsi]

firadisk32 = "FiraDisk Virtual Disk Driver x86"

firadisk64 = "FiraDisk Virtual Disk Driver x64"



[Files.scsi.firadisk32]

driver	 = d1, firadk32.sys, FiraDisk

inf		= d1, firadisk.inf

catalog	= d1, firadk32.cat



[Files.scsi.firadisk64]

driver	 = d1, firadk64.sys, FiraDisk

inf		= d1, firadisk.inf

catalog	= d1, firadk64.cat



[Config.FiraDisk]

value = "", DisplayName, REG_SZ, "FiraDisk Virtual Disk Driver"

value = "", ServiceType, REG_DWORD, 1

value = "", StartType, REG_DWORD, 0

value = "", ErrorControl, REG_DWORD, 1

value = "", Tag, REG_DWORD, 1

value = "", ServiceBinary, REG_SZ, "%12%\firadk32.sys"

value = "", LoadOrderGroup, REG_SZ, "SCSI miniport"

All I also do - change filenames to 8.3 format and corrected inf-sections for this filenames
What I do wrong, сan you help me?

#205 ireneuszp

ireneuszp

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    Poland

Posted 08 December 2009 - 02:01 PM

@kDn
I have the same error BSOD 0x000000ED: UNMOUNTABLE_BOOT_VOLUME :whistling:

#206 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 08 December 2009 - 08:48 PM

User fabvil must have hit by mistake the "report button" and sent to me this:
my variant:

[Disks]
d1 = "FiraDisk Installation Disk", \firadisk32.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,firadisk32.sys,firadisk
inf = d1,firadisk.inf

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

All works properly.


jaclaz

#207 af_pro

af_pro
  • Members
  • 2 posts

Posted 09 December 2009 - 09:21 AM

Please include more detail

Sorry, that was my mistake.
Now I can confirm the driver works perfectly, with fantastic speed.

#208 dickfitzwell

dickfitzwell

    Member

  • Members
  • 33 posts

Posted 15 December 2009 - 06:49 AM

I'm using the updated TXTSETUP.OEM reported to work by fabvil and still have this error with 0.0.1.16:

"The file firadisk32.sys could not be found."

I'm using grub4dos to load the floppy image as well as the XP CD. 0.0.1.12 worked previously. This happens in qemu as well as on a real machine.

Attached Files



#209 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 472 posts
  •  
    Thailand

Posted 15 December 2009 - 09:36 AM

@dickfitzwell
Do you have "firadisk32.sys" in your floppy image.

#210 af_pro

af_pro
  • Members
  • 2 posts

Posted 15 December 2009 - 02:38 PM

Download large image in memory, sometimes takes several minutes. It's not very pleasant to look at the black, frozen screen, some people begin to worry:).
Is there a working way to make this process visible, such as a counter, progress bar and the others?

#211 dickfitzwell

dickfitzwell

    Member

  • Members
  • 33 posts

Posted 15 December 2009 - 03:39 PM

@dickfitzwell
Do you have "firadisk32.sys" in your floppy image.

Yes! I extracted all the files to a virtual floppy drive image and loaded it via grub4dos and physical floppy drive A:, same error either way.

#212 jezza333

jezza333

    Member

  • Members
  • 47 posts
  •  
    Australia

Posted 17 December 2009 - 01:20 PM

I'm using the updated TXTSETUP.OEM reported to work by fabvil and still have this error with 0.0.1.16:

"The file firadisk32.sys could not be found."


I used to get the error - what you'll need to do is rename the sys files [it doesn't conform to the 8.3 file naming convention] and modify any references to them as required in the txtsetup.inf and firadisk.sys files. I get the BSOD though.

#213 yjstone

yjstone
  • Members
  • 4 posts

Posted 17 December 2009 - 05:21 PM

Yes! I extracted all the files to a virtual floppy drive image and loaded it via grub4dos and physical floppy drive A:, same error either way.

I got the same error with with 0.0.1.16,but with 0.0.1.12,it work well.

#214 zhaohj

zhaohj

    Newbie

  • Members
  • 10 posts
  •  
    China

Posted 18 December 2009 - 01:03 AM

firadisk0.0.1.16 version of Diskless Angel WDSYS drive instead of RAM, leading to RAMDISK of PE can not map - mem WINPE.ISO (0xff) so the overall start. The 0.14 and 0.12 version of normal.

#215 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 472 posts
  •  
    Thailand

Posted 18 December 2009 - 07:56 AM

Thanks for bug report.
I will fix it when I have time.

#216 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 472 posts
  •  
    Thailand

Posted 18 December 2009 - 10:39 PM

FiraDisk v0.0.1.18
Fix Windows XP 32-bit F6 incompatibility.
http://www.boot-land...?...ost&p=75606

#217 jezza333

jezza333

    Member

  • Members
  • 47 posts
  •  
    Australia

Posted 19 December 2009 - 02:14 PM

Thanks for the update. Sorry to be the bearer of bad news, but the new .18 release gives a BSOD in Windows XP setup when scripting a floppy image using GRUB. It didn't mention any specific errors, just that a problem was encountered and the PC needs to be shut down etc etc.

Oh well, v.12 works well enough at present ;)

#218 kDn

kDn

    Member

  • Members
  • 58 posts
  •  
    Ukraine

Posted 19 December 2009 - 02:59 PM

karyonix
Thank you. New version firadisk work without any problems for me.

jezza333
Can you give more information about error? Becouse I test FiraDisk v0.0.1.18 with XP_Inst method and all works excellent ( http://www.msfn.org/...r...57&t=137714 )

#219 jezza333

jezza333

    Member

  • Members
  • 47 posts
  •  
    Australia

Posted 21 December 2009 - 10:38 AM

Can you give more information about error? Becouse I test FiraDisk v0.0.1.18 with XP_Inst method and all works excellent ( http://www.msfn.org/...r...57&t=137714 )


Sure. This is roughly my menu.lst entry for installing XP...

title Begin setupsavedefault 1find --set-root /PATH_TO_ISOmap --mem /FIRADISK_FLOPPY (fd1)map --mem (md)0x6000+800 (fd0)map --mem /PATH_TO_ISO (hd32)map (hd1) (hd0)map (hd0) (hd1)map --hookdd if=(fd1) of=(fd0) count=1chainloader (hd32)title Continue setupsavedefault 0find --set-root /PATH_TO_ISOmap --mem /PATH_TO_ISO (hd32)map (hd1) (hd0)map (hd0) (hd1)map --hookchainloader (hd0)+1

I tried v.16 initially and had to revert to v.12. v.18 gives me a different BSOD than v.16 [which is UNSUPPORTED_BOOT_DEVICE]

#220 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 472 posts
  •  
    Thailand

Posted 21 December 2009 - 01:40 PM

@jezza333
Try this menu.lst.
[codebox]default 1 timeout 30 title Begin setup map (hd1) (hd0) map (hd0) (hd1) map --mem /FIRADISK_FLOPPY (fd0) map --mem /WINDOWS_ISO (hd32) map --hook chainloader (hd32)/I386/SETUPLDR.BIN title Continue setup (hd1) map (hd1) (hd0) map (hd0) (hd1) map --mem /WINDOWS_ISO (hd32) map --hook chainloader (hd0)+1 title Boot from (hd1) map (hd1) (hd0) map (hd0) (hd1)
map --hook
chainloader (hd0)+1[/codebox]

#221 jezza333

jezza333

    Member

  • Members
  • 47 posts
  •  
    Australia

Posted 22 December 2009 - 11:29 AM

Cheers for the help mate. I realised the error was on my part [I had created the floppy image but hadn't allocated 1.44MB, so it wasn't being mounted or read correctly] :merc:

Works fine with both menu versions now, as expected. Much appreciated. :cheers:

#222 zhaohj

zhaohj

    Newbie

  • Members
  • 10 posts
  •  
    China

Posted 23 December 2009 - 02:59 AM

firadisk0.0.1.18 Edition startup problems have been resolved as a whole are extremely grateful!

#223 i

i

    Silver Member

  • Advanced user
  • 539 posts
  •  
    United Nations

Posted 31 January 2010 - 01:47 PM

Hi ;) I have a quick question (really can't go through all the documentations for it :lol:)


Is there a way to make FiraDisk driver only use RAM space above 32Bit address limit using PAE? For example I've 8GB RAM however, XP x86 can see 3.25GB right? (4.75 unseen!) So, any way to make File or RamDisk loaded only on that "unseen" 4.75 GB? (without affecting 3.25GB which windows sees?

I'm already using Ggavotte or something Ramdisk from here, which does excellent job ;)

#224 TheK

TheK

    Frequent Member

  • Advanced user
  • 141 posts
  • Location:Germany (BW)
  •  
    Germany

Posted 31 January 2010 - 02:56 PM

That's possible using Grub4dos with PAE support :lol:

#225 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 472 posts
  •  
    Thailand

Posted 31 January 2010 - 04:55 PM

Use latest experimental GRUB4DOS http://grub4dos-chen...-2010-01-23.zip .
AND
Use command "map --mem-min=4G" before "map --mem /filename (hd0)".
Or use command "map --mem --top /filename (hd0)".
Or use image larger than 3.25GB. See example in Windows 7 RC x86 in 4.75 GB RAM disk .




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users