I am still implementing and testing a new NTFS driver for my disc, it probably won't be released for a few more days.
Oh, and for those who are wondering, your Windows drivers (like PortIO) have absolutely no effect on my disc. My disc doesn't use Windows drivers at all.
Also, just to clarify, Hitachi-LG drives are not supported by my disc. Please do not attempt to use any Hitachi-LG drive with my disc, or your could brick your drive or worse. My disc does not currently support the Hitachi-LG GDR-3120L at all.
QUOTE(brauntje @ Mar 10 2009, 06:46 PM)
![*](style_images/1/post_snapback.gif)
Hey Frosty,
first of all thank you very much for your hard work on this. The mod disc is really easy to work with and very clear. I have worked with the 1.5 version a while now and it worked perfect for me.
But when i try to use the 1.51 version it won't write to the c: drive anymore, when I type, samsung, benq or liteon it says that it failed to write to A. I can ignore that, but when I go on I can dump the firmware but it can't inject any code because it doesn't dump it anywhere I think.
And the difference i noticed with the 1.5 version that the 1.5 version shows X: as my cd drive and A: as the c drive (sounds logic to me). But the 1.51 version shows the A: drive as cd drive and because of that it can't write to the A drive.
Do you know a way to solve this problem and are there more people with the same problem?
Thanks in advance, and Kudos for your work!
My v1.5 disc used a 1.44MB floppy image as the boot image on my CD, but the new version (v1.51) uses a 2.88MB floppy image instead, which your BIOS may not like. Have you tried using my disc on another PC by chance?
I had to switch over to a 2.88MB boot image due to the size of the modification files and script, and because so many people were having problems with the CD-ROM driver I was using on v1.5. My new disc makes your PC think it's simply a bootable 2.88MB floppy instead of relying on CD-ROM drivers, so the 2.88MB boot image might cause issues with some motherboards. (although most new motherboards should handle it just fine, I use an old MSI motherboard for my test bench)
Also, none of my discs ever write to the A: drive anyway, they write to a hidden RAMDISK (which is the T: drive)... as far as I know you are the only user to have reported this issue...