Jump to content











Photo
* * * * * 7 votes

FiraDisk (latest = 0.0.1.30)


  • Please log in to reply
624 replies to this topic

#151 Marietto

Marietto

    Frequent Member

  • Advanced user
  • 268 posts
  • Location:Italy
  • Interests:Computers,movies,read/write,talking about philosophy and religion.
  •  
    Italy

Posted 25 October 2009 - 08:16 PM

....

#152 ilko

ilko

    Silver Member

  • Advanced user
  • 500 posts
  •  
    Bulgaria

Posted 27 October 2009 - 12:18 AM

Testing Windows setup from ram booted ISO and Firadisk 0.0.1.12 on a virtual floppy.
http://www.boot-land...?...ost&p=76936
http://www.boot-land...?...ost&p=77011

Test on both QEMU and real hardware with 1GB RAM, ISO files ~600MB.

Server 2003 SP1 32 bit-->BSOD 0x0000007B
Server 2003 SP2 32 bit-->BSOD 0x0000007B
XP Pro SP2 32 bit --> works
XP Pro SP3 32 bit --> works
WinFLPC --> works
2000 SP4 -->BSOD 0x0000007B

Questions:
- any plans to support Windows 2000 ?
- why 2003 32-bit bluescreens, can I help you anyhow in troubleshooting this one?
- any plans for XP/2003 x64 versions ? Would it require a lot of coding?

Thanks for the great work, it is awesome :confused1:

#153 Lancelot

Lancelot

    Frequent Member

  • .script developer
  • 5013 posts
  • Location:Turkiye/Izmir
  • Interests:*Mechanical stuff and Physics,
    *LiveXP, BartPE, SherpyaXPE,
    *Basketball and Looong Walking,
    *Buying outwear for my girlf (Reason: Girls are stupid about buying bad stuff to make themselves uglier :))
    *Girls (Lyric: Girl,...., You will be a womann, Soon)
    *Answering questions for "Meaning of life",
    *Helping people,

    Kung with LiveXP, Fu with Peter :)
  •  
    Turkey

Posted 27 October 2009 - 01:20 AM

For the record: firadisk x64 works with experimantal PE1x64 booting. (PE1x64.iso boots fine with menu.lst)
title pe1x64.iso

find --set-root /pe1x64.iso

map --mem /pe1x64.iso (0xFF)

map --hook

chainloader (0xFF)

besides, sth interesting happens,

on pe1x86.iso builds, test.img is accesable on PE with booting cd by these:

title Test -- SETUPLDR.BIN + img

chainloader /I386/SETUPLDR.BIN

map --mem /test.img (hd22,0)

map --hook

on pe1x64.iso builds, test.img is not accesable

title Test -- SETUPLDR.BIN + img

chainloader /AMD64/SETUPLDR.BIN

map --mem /test.img (hd22,0)

map --hook

tested with 0.0.1.12
maybe this test result helps.. :confused1:

#154 pseudo

pseudo
  • Members
  • 8 posts
  •  
    China

Posted 29 October 2009 - 05:38 PM

Several User In bbs.wuyou.com reported that if the Windows PE uses firadisk driver, then the PE using GHOST to clone windows xp will fail to restart.
This prompt will appear:

A disk read error occurred
Press Ctrl + Alt + Del to restart

This is the original topic(in Chinese):http://bbs.wuyou.com/viewthread.php?tid=153518&extra=page%3D3

You can use "chainloader / ntldr" to boot from the hard disk once, it can fix the problem, and then next time you can normally started from the hard disk.
(Correction: chainloader /ntldr can boot from the hard disk, but it can not fix the problem.Thanks jaclaz)

0PE and MicroPE (their menu items are listed in grub4dos sample menu file menu.lst) have used firadisk, they all experience this problem.

If the real firadisk.sy_ be replaced with Diskless Angel driver wdsys.sys (packaged as firadisk.sy_), then everything is normal.

#155 was_jaclaz

was_jaclaz

    Finder

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

Posted 29 October 2009 - 06:34 PM

Several User In bbs.wuyou.com reported that if the Windows PE uses firadisk driver, then the PE using GHOST to clone windows xp will fail to restart.
This prompt will appear:

This is the original topic(in Chinese):http://bbs.wuyou.com/viewthread.php?tid=153518&extra=page%3D3

You can use "chainloader / ntldr" to boot from the hard disk once, it can fix the problem, and then next time you can normally started from the hard disk.

0PE and MicroPE (their menu items are listed in grub4dos sample menu file menu.lst) have used firadisk, they all experience this problem.

If the real firadisk.sy_ be replaced with Diskless Angel driver wdsys.sys (packaged as firadisk.sy_), then everything is normal.


From the (very little I can understand from your report and form the Chinese reference) it seems to me like there is a kind of "sticky" problem during a WARM reboot. ;)

Doing a COLD reboot should work allright. :unsure:

Running "chainloader /ntldr" from grub4dos CANNOT "repair" a supposedly wrong MBR, thus the problem must somehow be in RAM.

Can you try to describe in more detail what happens, I am afraid that "then the PE using GHOST to clone windows xp will fail to restart. " is not understandable enough.

:confused1:

jaclaz

#156 pseudo

pseudo
  • Members
  • 8 posts
  •  
    China

Posted 02 November 2009 - 04:15 PM

I have used DiskGenius in PE to detect the H and S parameters of physical hard disk and found that they are the same as those of the virtual disk X: which is supported by firadisk.
For example, a hard disk with parameters H = 255, S = 63 will be seen as a disk with parameters H = 80, S = 32.

These parameters may be written to the partition table, BPB of partition boot record during partition, format, ghost somehow.

If you package the Diskless Angel driver wdsys.sys into firadisk.sy_, pretending to really firadisk.sy_, then the parameters of physical hard disk are different to those of virtual disk X:.

#157 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 02 November 2009 - 05:25 PM

I still don't understand.
You use GHOST to clone Windows.
How does GHOST clones Windows ?
- by copying files or partition or whole disk ?
- from where ? to where ?
How does firadisk involve in your cloning process ?

#158 zhaohj

zhaohj

    Newbie

  • Members
  • 10 posts
  •  
    China

Posted 04 November 2009 - 02:34 AM

In the non-sorrow forum CHENALL MICROPE and PSEUDO 0PE, the use hypothesized disk actuates with FIRADISK.SYS to replace the non-plate angel actuation WDSYS.SYS, uses GHOST32.exe under PE the document to the district (the c plate) the operation, has the hard disk district table change.

The GHO document is the normal XP system clone document, under PE GHOSE32 with the district to the district operation, under PE restores completes starts the system with the hard disk, appears the disk error message:

A disk read error occurred
Press Ctrl + Alt + Del to restart

Attached Files

  • Attached File  Snap1.jpg   130.33KB   13 downloads
  • Attached File  Snap2.jpg   127.03KB   14 downloads
  • Attached File  1.rar   214.03KB   15 downloads


#159 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 04 November 2009 - 06:12 AM

@pseudo, zhaohj
Is this correct ?
1. You use GRUB4DOS to load hard disk image to RAM and boot Windows PE from RAM drive.
2. When running from RAM, geometry of real hard disk appears to be incorrect.
3. You restore a partition from ghost image to real hard disk partition.
4. After restored you cannot boot from real hard disk partition boot record but can boot from chainloader /ntldr.

Please post your menu.lst that you use to load disk image into RAM when you boot from RAM in step 1.

#160 pseudo

pseudo
  • Members
  • 8 posts
  •  
    China

Posted 04 November 2009 - 06:13 AM

Zhaohj is a VIP of bbs.wuyou.com forum who firstly reports the problem and has first-hand information about ghost in 0PE and MicroPE.

In the two PEs mentioned above, an img made by imdisk is mapped as a hard disk, equivalents to:

map --mem ()/0PE/BUFXP.IMG.GZ (hd0)
map --hook=0x80
chainloader (hd0,0)/setupldr.bin

Supportted by firadisk, the grub4dos mapped disk (hd0) in memory would become to a virtual hard disk X: which holding PE system files.

Firadisk.sy_ is in wxpe\system32\drivers,and firadisk.inf is in wxpe\inf, here wxpe is the systemroot of PE. The txtsetup.oem has the following sections:

[ScsiClass.Load]
cdrom=cdrom.sys
disk=disk.sys
firadisk=firadisk.sys
[ScsiClass]
cdrom="SCSI CD-ROM"
disk="SCSI Disk"
firadisk="FiraDisk Virtual Disk Driver"



#161 pseudo

pseudo
  • Members
  • 8 posts
  •  
    China

Posted 04 November 2009 - 06:36 AM

@pseudo, zhaohj
Is this correct ?
1. You use GRUB4DOS to load hard disk image to RAM and boot Windows PE from RAM drive.
2. When running from RAM, geometry of real hard disk appears to be incorrect.
3. You restore a partition from ghost image to real hard disk partition.
4. After restored you cannot boot from real hard disk partition boot record but can boot from chainloader /ntldr.

Please post your menu.lst that you use to load disk image into RAM when you boot from RAM in step 1.

Yes, you made a good summary of our statements, I think.
The menu.lst in 0PE is too long and complex to list here(over 20K), but I think it is equivalent to the 3 lines listed above.

Some 0PE users have reported about ghost's restart problem and I and Chenall(the MicroPE's author)have also occurred the problem. But I can't repeat the ghost problem now in VMware. I can only find the geometry of real hard disk appears to be incorrect in DiskGenius.

#162 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 04 November 2009 - 06:41 AM

I think you hide real (hd0) from Windows boot loader, so Windows does not know its BIOS disk geometry.
Please try mapping real (hd0) to other drive number.
map (hd0) (hd1)

map --mem ()/0PE/BUFXP.IMG.GZ (hd0)

map --hook

chainloader (hd0,0)/setupldr.bin


#163 pseudo

pseudo
  • Members
  • 8 posts
  •  
    China

Posted 04 November 2009 - 07:07 AM

I think you hide real (hd0) from Windows boot loader, so Windows does not know its BIOS disk geometry.
Please try mapping real (hd0) to other drive number.

map (hd0) (hd1)

map --mem ()/0PE/BUFXP.IMG.GZ (hd0)

map --hook

chainloader (hd0,0)/setupldr.bin

In fact, I had used
map (hd0) (hd1)
to keep physical (hd0) accesssiable as (hd1), and used
map --unmap=0,1,2,0x81:0xfe

map --rehook
to release (hd1) mapping before
chainloader (hd0,0)/setupldr.bin
It works fine with wdsys.

#164 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 04 November 2009 - 08:30 AM

Don't unmap 0x81.

#165 zhaohj

zhaohj

    Newbie

  • Members
  • 10 posts
  •  
    China

Posted 05 November 2009 - 01:56 AM

After Don't unmap 0x81 the question solution, uses under FIRADISK actuation PE to examine the hard disk district is normal, thanks extremely!

#166 PatrickF

PatrickF

    Newbie

  • Members
  • 15 posts
  •  
    Germany

Posted 05 November 2009 - 01:20 PM

Hi,

is it possible to use FiraDisk with Windows 7 32Bit Ultimate? Is it Stable?
I created the following scenario:
- Win7 32Bit Install in VHD
- Booticing USB Stick/Drive
- Copying vhd
- Editing bcd configuration
- Installing FiraDisk in Windows
- Mounting C:\image.raw to X:\ using FiraDisk
- Tell Windows to use pagefile.sys on X:\
- Disabling all other pagefiles

But sometimes I the system freezes, maybe this has something to do with FiraDisk? or have you another idea?
SystemRam is about 2GB; Pagefile size about 1GB

Background: I need the pagefile on the USB Drive itself, because i need to image the main harddrive using Ghost32 which cannot create images from drives which are active.


greets
patrick

#167 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 05 November 2009 - 02:27 PM

@PatrickF
I have not tested Windows 7 32-bit much.

I think pagefile in RAM disk (of FiraDisk) is OK.
But it may not work well in FiraDisk's VirtualMem disk or FiraDisk's File disk.

--------

@ilko and everyone
http://www.mediafire...er-0.0.1.14.zip
32-bit driver in this package is compiled with Windows 2000 build environment but I don't have Windows 2000 to test it.
At least in works in Windows XP 32-bit. Not sure about other OS versions.

#168 ilko

ilko

    Silver Member

  • Advanced user
  • 500 posts
  •  
    Bulgaria

Posted 06 November 2009 - 12:59 AM

...@ilko and everyone
http://www.mediafire...er-0.0.1.14.zip
32-bit driver in this package is compiled with Windows 2000 build environment but I don't have Windows 2000 to test it.
At least in works in Windows XP 32-bit. Not sure about other OS versions.


Firadisk 0.0.1.12						  QEMU 0.9.1	|	 PC1   |   PC2	 |   PC3

-------------------

2003  SP1 32-bit							0x7B		 |	 0x7B  |   0x7B	|  hang at partition screen

2003  SP2 32-bit							0x7B		 |	 0x7B  |   0x7B	|  worked

XP SP3									  worked	   |   worked  |  worked   |  worked

2000 SP4									0x7B		 |	 0x7B  |   0x7B	|   0x7B

2003 SP2 64-bit							 n/a		  |screenshot |screenshot |   n/a

Posted Image


Firadisk 0.0.1.14						  QEMU 0.9.1	|	 PC1   |   PC2	 |   PC3

-------------------

2003  SP1 32-bit							0x7B		 |	 0x7B  |   0x7B	|  worked

2003  SP2 32-bit							0x7B		 |	 0x7B  |   0x7B	|  worked

XP SP3									  worked	   |   worked  |  worked   |  worked

2000 SP4									0x7B		 |	 0x7B  |   0x7B	|   0x7B

2003 SP2 64-bit							 n/a		  |screenshot |screenshot |   n/a

PC1: Relatively old Intel chipset based desktop, Core2Duo, 1x DVD, 1 x floppy
PC2: Relatively new Intel chipset based desktop, Core2Duo, no CD/DVD, no floppy
PC3: Dell mini 10, no CD/DVD, no floppy

menu.lst
...

title Windows Server 2000

ls /Inst/2000.ISO || find --set-root /Inst/2000.ISO

map --mem /Inst/XP_INST.IMA (fd0)

map --mem /Inst/XP_INST.IMA (fd1)

map --mem /Inst/2000.ISO (0xFF)

map --hook

chainloader (0xFF)/I386/SETUPLDR.BIN

...

txtsetup.oem in XP_INST.IMA
[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

Desktops are set to IDE compatible mode.
Tried with map (hd32), (0xA0), root (0xFF), mapping one floppy only, loading the ISO images from internal and external USB HD- same results.

It's surprise how this Dell mini slipped through and loaded 2k3 32-bit. Grub4dos versions 0.4.4 / 2009-05-23 and 0.4.4 / 2009-10-16.

#169 corsair

corsair
  • Members
  • 3 posts
  •  
    United States

Posted 06 November 2009 - 11:49 PM

@karyonix
Its been awhile since I came back to this.

Has the speed improved of the driver?
Last I did win2k3sp2 the HDTACH disk benchmark tool showed only 30MB/s write/read.
I could notice it fairly slow despite being on ram. I dont see this speed issue with ramdisk.sys driver.

#170 ireneuszp

ireneuszp

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    Poland

Posted 07 November 2009 - 09:02 PM

Firadisk 0.0.1.12						  QEMU 0.9.1	|	 PC1   |   PC2	 |   PC3

-------------------

2003  SP1 32-bit							0x7B		 |	 0x7B  |   0x7B	|  hang at partition screen

2003  SP2 32-bit							0x7B		 |	 0x7B  |   0x7B	|  worked

XP SP3									  worked	   |   worked  |  worked   |  worked

2000 SP4									0x7B		 |	 0x7B  |   0x7B	|   0x7B

2003 SP2 64-bit							 n/a		  |screenshot |screenshot |   n/a

Posted Image


Firadisk 0.0.1.14						  QEMU 0.9.1	|	 PC1   |   PC2	 |   PC3

-------------------

2003  SP1 32-bit							0x7B		 |	 0x7B  |   0x7B	|  worked

2003  SP2 32-bit							0x7B		 |	 0x7B  |   0x7B	|  worked

XP SP3									  worked	   |   worked  |  worked   |  worked

2000 SP4									0x7B		 |	 0x7B  |   0x7B	|   0x7B

2003 SP2 64-bit							 n/a		  |screenshot |screenshot |   n/a

PC1: Relatively old Intel chipset based desktop, Core2Duo, 1x DVD, 1 x floppy
PC2: Relatively new Intel chipset based desktop, Core2Duo, no CD/DVD, no floppy
PC3: Dell mini 10, no CD/DVD, no floppy

menu.lst
...

title Windows Server 2000

ls /Inst/2000.ISO || find --set-root /Inst/2000.ISO

map --mem /Inst/XP_INST.IMA (fd0)

map --mem /Inst/XP_INST.IMA (fd1)

map --mem /Inst/2000.ISO (0xFF)

map --hook

chainloader (0xFF)/I386/SETUPLDR.BIN

...

txtsetup.oem in XP_INST.IMA
[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

Desktops are set to IDE compatible mode.
Tried with map (hd32), (0xA0), root (0xFF), mapping one floppy only, loading the ISO images from internal and external USB HD- same results.

It's surprise how this Dell mini slipped through and loaded 2k3 32-bit. Grub4dos versions 0.4.4 / 2009-05-23 and 0.4.4 / 2009-10-16.


try my firadisk.img

Attached Files



#171 ilko

ilko

    Silver Member

  • Advanced user
  • 500 posts
  •  
    Bulgaria

Posted 07 November 2009 - 11:23 PM

try my firadisk.img

QEMU and real hardware with 2003 SP1, 2 and XP SP3 behaved exactly as before.

What's actually your point, what's different? That the floppy image is compressed? Or that the different file names matter?
Did you try with the sources described and had success? On what hardware? Using what source?

#172 ireneuszp

ireneuszp

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    Poland

Posted 08 November 2009 - 03:12 PM

QEMU and real hardware with 2003 SP1, 2 and XP SP3 behaved exactly as before.

What's actually your point, what's different? That the floppy image is compressed? Or that the different file names matter?
Did you try with the sources described and had success? On what hardware? Using what source?


here is my screen shot from quemu (winxp + firadisk.img) and it works ok
on real pc it also works

in grub4dos I have
title xpsp3.iso...\n (--mem firadisk.img & --mem xpsp3.iso)

find --set-root /images/firadisk.img

map --mem /images/firadisk.img (fd0)

map --mem /images/xpsp3.iso (0xff)

map --hook

chainloader (0xff)

Attached Files



#173 ilko

ilko

    Silver Member

  • Advanced user
  • 500 posts
  •  
    Bulgaria

Posted 08 November 2009 - 04:24 PM

Please read carefully the results I posted.
XP was success with both latest versions of Firadisk on all machines. Troubles are with other windows versions...

#174 ilko

ilko

    Silver Member

  • Advanced user
  • 500 posts
  •  
    Bulgaria

Posted 08 November 2009 - 09:07 PM

Here is debug output of Windows 2000 setup on VMWare Workstation 5.5.5 and Firadisk 0.0.1.14:
[codebox]Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Opened \\.\pipe\com_1 Waiting to reconnect... Connected to Windows 2000 2195 x86 compatible target at (Sun Nov 8 12:56:38.515 2009 (GMT-8)), ptr64 FALSE Kernel Debugger connection established. Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 2000 Kernel Version 2195 MP (1 procs) Free x86 compatible Machine Name: Kernel base = 0x80400000 PsLoadedModuleList = 0x80484520 System Uptime: not available FiraDisk: DriverEntry start ---------- FiraDisk: DriverEntry success FiraDisk: BootDriverReinitialize 1 ---------- FiraDisk: FindAdapter Calling IoReportDetectedDevice FiraDisk: FindAdapter IoReportDetectedDevice status=0x0 FiraDisk: AddDevice start FiraDisk: AddDevice success FiraDisk: BusStart FiraDisk: Read Options status=0xC0000034 FiraDisk: map real-mode memory success FiraDisk: int13=9c80:0100 FiraDisk: GRUB4DOS at 9c80:0100 FiraDisk: Detected RAM drive class=3 addr=0x3f188000 len=1474560 bps=512 spt=18 tpc=2 FiraDisk: Detected RAM drive class=3 addr=0x3f020000 len=1474560 bps=512 spt=18 tpc=2 FiraDisk: Detected RAM drive class=2 addr=0x31131000 len=233762816 bps=2048 spt=63 tpc=255 FiraDisk: int13=ebea:25fc FiraDisk: Create RAM drive class=3 addr=0x3f188000 len=1474560 bps=512 spt=18 tpc=2 FiraDisk: FDOCreatePhysicalMemDisk start FiraDisk: FDOCreatePhysicalMemDisk success FiraDisk: Create RAM drive class=3 addr=0x3f020000 len=1474560 bps=512 spt=18 tpc=2 FiraDisk: FDOCreatePhysicalMemDisk start FiraDisk: FDOCreatePhysicalMemDisk success FiraDisk: Create RAM drive class=2 addr=0x31131000 len=233762816 bps=2048 spt=63 tpc=255 FiraDisk: FDOCreatePhysicalMemDisk start FiraDisk: FDOCreatePhysicalMemDisk success FiraDisk: Read Options status=0xC0000034 FiraDisk: ChildStartDrive FiraDisk: Starting FiraDisk: RAM length=1474560 addr=0x3f188000 FiraDisk: Drive started bytes=1474560 sectors=2880 b/s=512 FiraDisk: Device Ready FiraDisk: ChildStartDrive FiraDisk: Starting FiraDisk: RAM length=1474560 addr=0x3f020000 FiraDisk: Drive started bytes=1474560 sectors=2880 b/s=512 FiraDisk: Device Ready FiraDisk: ChildStartDrive FiraDisk: Starting FiraDisk: RAM length=233762816 addr=0x31131000 FiraDisk: Drive started bytes=233762816 sectors=114142 b/s=2048 FiraDisk: Device Ready FiraDisk: FindAdapter end *** Fatal System Error: 0x0000007b (0xF2467848,0xC0000034,0x00000000,0x00000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows 2000 2195 x86 compatible target at (Sun Nov 8 12:57:14.828 2009 (GMT-8)), ptr64 FALSE Loading Kernel Symbols ............................................................... .................... Loading User Symbols PEB address is NULL ! Loading unloaded module list .. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7B, {f2467848, c0000034, 0, 0} PEB address is NULL ! PEB address is NULL ! Probably caused by : ntkrnlmp.exe ( nt!IopMarkBootPartition+bd ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 804564d0 cc int 3 kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INACCESSIBLE_BOOT_DEVICE (7b) During the initialization of the I/O system, it is possible that the driver for the boot device failed to initialize the device that the system is attempting to boot from, or it is possible for the file system that is supposed to read that device to either fail its initialization or to simply not recognize the data on the boot device as a file system structure that it recognizes. In the former case, the argument (#1) is the address of a Unicode string data structure that is the ARC name of the device from which the boot was being attempted. In the latter case, the argument (#1) is the address of the device object that could not be mounted. If this is the initial setup of the system, then this error can occur if the system was installed on an unsupported disk or SCSI controller. Note that some controllers are supported only by drivers which are in the Windows Driver Library (WDL) which requires the user to do a custom install. See the Windows Driver Library for more information. This error can also be caused by the installation of a new SCSI adapter or disk controller or repartitioning the disk with the system partition. If this is the case, on x86 systems the boot.ini file must be edited or on ARC systems setup must be run. See the "Advanced Server System Administrator's User Guide" for information on changing boot.ini. If the argument is a pointer to an ARC name string, then the format of the first two (and in this case only) longwords will be: USHORT Length; USHORT MaximumLength; PWSTR Buffer; That is, the first longword will contain something like 00800020 where 20 is the actual length of the Unicode string, and the next longword will contain the address of buffer. This address will be in system space, so the high order bit will be set. If the argument is a pointer to a device object, then the format of the first word will be: USHORT Type; That is, the first word will contain a 0003, where the Type code will ALWAYS be 0003. Note that this makes it immediately obvious whether the argument is a pointer to an ARC name string or a device object, since a Unicode string can never have an odd number of bytes, and a device object will always have a Type code of 3. Arguments: Arg1: f2467848, Pointer to the device object or Unicode string of ARC name Arg2: c0000034 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB address is NULL ! PEB address is NULL ! DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x7B PROCESS_NAME: System LAST_CONTROL_TRANSFER: from 8042aa0f to 804564d0 STACK_TEXT: f2467340 8042aa0f 00000003 f2467388 f2467848 nt!RtlpBreakWithStatusInstruction f2467370 8042b002 00000003 8046edc0 00000000 nt!KiBugCheckDebugBreak+0x31 f24676fc 8054b9d1 0000007b f2467848 c0000034 nt!KeBugCheckEx+0x390 f2467860 8054b216 80084000 80084000 000000bb nt!IopMarkBootPartition+0xbd f24678b4 80549c86 80084000 f24679fc 00000000 nt!IopInitializeBootDrivers+0x440 f2467a54 80548b4c 80084000 00000000 00000000 nt!IoInitSystem+0x5ef f2467da8 80455a82 80084000 00000000 00000000 nt!Phase1Initialization+0x7e2 f2467ddc 8046b012 8054836a 80084000 00000000 nt!PspSystemThreadStartup+0x54 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!IopMarkBootPartition+bd 8054b9d1 8d4508 lea eax,[ebp+8] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!IopMarkBootPartition+bd FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 3ee650b3 FAILURE_BUCKET_ID: 0x7B_nt!IopMarkBootPartition+bd BUCKET_ID: 0x7B_nt!IopMarkBootPartition+bd Followup: MachineOwner ---------[/codebox] As far as I interpret it, Firadisk finds 3 devices and creates virtual drives for them, right?

BTW- 2003 32-bit SP1 setup booted fine in VMWare, just as on the Dell mini :dubbio:

#175 maanu

maanu

    Gold Member

  • Advanced user
  • 1134 posts
  •  
    Pakistan

Posted 08 November 2009 - 11:19 PM

have your tried pseudo's OPE method to install 2k3 ? he mentioned to me tonight that his new version has been very improved to work with new firadisk and 2k3 or xp install. on sata specially .




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users