119 replies to this topic

[agni]

Thanks Vortex.You saved me a lot of time and bandwidth as I don't have to download the second disc.

[Sha0]

Does MEMDISK survive wiping ?

It doesn't get wiped as it marks itself as unusable in the E820 map. For example (G4D syntax):

kernel /memdisk pause

initrd /g4d.vfd

where g4d.vfd is a floppy image with GRUB4DOS on it. Thanks to pause, MEMDISK will show before-and-after info about E820. Then displaymem from the booted G4D will confirm. This is fortunately a very easy test to perform in QEmu.

[karyonix]

Please try this one.
(link removed)

Previous test build just remove memory range occupied by int13_handler.
This test build returns memory range occupied by int13_handler as type reserved.
Adding code results in int13_handler being larger than 12KB.

EDIT
Vortex reported menu problem with previous build.
Here is new build. (2011-02-03)
http://www.mediafire...1-02-03-test.7z

[Vortex]

Hi karyonix,

Thanks for your grub4dos release. The tests with your grldr version were performed on two different computers. Here is my report.

Test1 :

title 2003 setup



map /Srv2003.img (hd0)

map --mem /winvblock.ima (fd0)

map /Server2003.iso (0xff)

map --hook

chainloader (0xff)/I386/SETUPLDR.BIN



title Continue 2003 setup



map /Srv2003.img (hd0)

map --mem /winvblock.ima (fd0)

map /Server2003.iso (0xff)

map --hook

root (hd0,0)

chainloader /ntldr

HAL1 : ACPI Multiprocessor computer, Intel D865GSA motherboard

The installer starts the text phase of the Server 2003 setup and everything is freezing after the message "Setup is starting windows"

HAL2 : ACPI Uniprocessor computer ,an old Gigabyte motherboard bought in early 2004

The installation is succesfull and no any problem.

Test2 :

title 2003 setup



map (hd0) (hd1)

map /Srv2003.img (hd0)

map --mem /winvblock.ima (fd0)

map --hook

kernel (hd1,0)/memdisk iso pause

initrd (hd1,0)/Server2003.iso



title Continue 2003 setup



map /Srv2003.img (hd0)

map --mem /winvblock.ima (fd0)

map /Server2003.iso (0xff)

map --hook

root (hd0,0)

chainloader /ntldr

HAL1 : ACPI Multiprocessor computer

TRAP 00000006 Exception

HAL2 : ACPI Uniprocessor computer

The installation is succesfull and no any problem.

I guess that the problem with Server 2003 is associated with the ACPI Multiprocessor HAL. Sha0 mentioned that there could be an issue related to the HAL type.

Edited by Vortex, 29 January 2011 - 11:25 AM.

[Wonko the Sane]

I guess that the problem with Server 2003 is associated with the ACPI Multiprocessor HAL. Sha0 mentioned that there could be an issue related to the HAL type.

If this is the problem, it should be possible to "force" the "Standard PC" HAL at install and later change it?


Wonko

[Vortex]

Hi Wonko,

Some days ago, the idea of forcing another HAL at the startup came to my mind. Today, I tried it again with karyonix's grldr release. Unfortunately, the same freezing issue happened on the ACPI Multiprocessor HAL system: The setup begins the text phase. You hit F5 and select Standard PC HAL. A little later after displaying the message "Setup is starting windows" , the installer remains irresponsive and your only choice is to touch the power button to shutdown the system.

title 2003 setup



map /Srv2003.img (hd0)

map --mem /winvblock.ima (fd0)

map /Server2003.iso (0xff)

map --hook

chainloader (0xff)/I386/SETUPLDR.BIN

The memdisk method throws the TRAP 0000006 exception before the Server 2003 installer takes action.

Anyway, thanks for your suggestion to switch to another HAL type.

[Wonko the Sane]

Hi Wonko,

Some days ago, the idea of forcing another HAL at the startup came to my mind. Today, I tried it again with karyonix's grldr release. Unfortunately, the same freezing issue happened on the ACPI Multiprocessor HAL system: The setup begins the text phase. You hit F5 and select Standard PC HAL. A little later after displaying the message "Setup is starting windows" , the installer remains irresponsive and your only choice is to touch the power button to shutdown the system.

Yep , (actually meaning , I did word very badly the suggestion), it should have been more like :

Would the "ACPI Uniprocessor HAL" (Halaacpi.dll) - that should be the one that worked on PC #2 - work on PC #1 if Forced with the F5?

According to this:
http://support.micro...kb/309283/en-us
the switch between "ACPI Uniprocessor PC" (Halaacpi.dll) and the "ACPI Multiprocessor" (Halmacpi.dll) should be possible easily from within the booted OS.


Wonko

[Vortex]

Hi Wonko,

Thanks for the link to MS article. I guess the only option to switch to another HAL before Windows setup is to hit F5. We have to find a solution for the Multiprocessor HAL issue because today's new processors are not designed anymore to conform only the Uniprocessor specification. What I mean is that when you install Windows on systems with multi-core CPUs ( at least XP or Server 2003 ) you see a Multiprocessor HAL not an Uniprocessor HAL type.

[Wonko the Sane]

Hi Wonko,

Thanks for the link to MS article. I guess the only option to switch to another HAL before Windows setup is to hit F5. We have to find a solution for the Multiprocessor HAL issue because today's new processors are not designed anymore to conform only the Uniprocessor specification. What I mean is that when you install Windows on systems with multi-core CPUs ( at least XP or Server 2003 ) you see a Multiprocessor HAL not an Uniprocessor HAL type.

Yes. That's is the "by design" the installer, strangely enough it does works rightly and selects the "right" HAL, point is to find out IF the "ACPI uniprocessor" (Halaacpi.dll) (forced with F5) works with Winvblock or Firadisk.
If it does, there is no problem in switching it later.


Wonko

[Vortex]

I repeated my tests with firadisk on my ACPI Multiprocessor system. The grub4dos settings are the same as in my posting #79 :

http://reboot.pro/13...post__p__120708

The setupldr.bin method displayed a BSDO with 7B after displaying "Setup is starting windows"
The other memdisk method throwed again TRAP 00000006 exception.

[Sha0]

...The other memdisk method throwed again TRAP 00000006 exception...

That one is is going to have to be investigated sooner or later. The good news is that if it's a MEMDISK bug, it can be fixed. Testing a MEMDISK from Syslinux <= 3.82 might be interesting... WinVBlock won't support such a MEMDISK, but it might be good to know if the TRAP still occurs; MEMDISK was changed fairly significantly at one point after Syslinux 3.82, so that could narrow down the problem.

[Vortex]

Hi Sha0,

Here is my report with Syslinux 3.80 I downloaded the package from this site :

http://mirror.muntin...x/boot/syslinux

Testing the configuration on my ACPI Multiprocessor system :

title 2003 setup



map (hd0) (hd1)

map /Srv2003.img (hd0)

map --mem /winvblock.ima (fd0)

map --hook

kernel (hd1,0)/memdisk iso pause

initrd (hd1,0)/Server2003.iso

memdisk loaded the .iso file and displayed the expected message :

Loading boot sector... Press any key to boot

Pressing a key, it displays :

booting

The screen freezes and no continuation. No any exception occurred.

Edited by Vortex, 30 January 2011 - 04:58 PM.

[Sha0]

...Here is my report with Syslinux 3.80 I downloaded the package from this site...
The screen freezes and no continuation. No any exception occurred.

Thanks, Vortex! Yes that version of MEMDISK was before the iso (.ISO) support. BUT, it's still good to know that it didn't cause the exception!

[Vortex]

Hi Sha0,

Can we expect a new release of memdisk fixing the HAL issue?

[Sha0]

...Can we expect a new release of memdisk fixing the HAL issue?

I'd need to reproduce it, first... Just been doing some other things... There's been some other recent MEMDISK work, so this can be added to that active list of considerations.

[cdob]

@Vortex
Try remove RAM floppy, use direct mapping:

map /winvblock.ima (fd0)

[Vortex]

@Vortex
Try remove RAM floppy, use direct mapping:

map /winvblock.ima (fd0)

Hi cdob,

Thanks, I tried your suggestion but the result is the same : BSOD with error code 7B

[cdob]

Thanks, I tried your suggestion but the result is the same : BSOD with error code 7B

XP install from RAM disk did 'screen freezes and no continuation' at some machines.
Sad, this seems to be another issue. Sorry no further idea.

[davlak]

ehi guys you're really great!
my humble experience and little feedback
I finally succeded into intalling 2003 on a img\vhd, using the karyonix modified grldr and theese lines

title Setup 2003 via WinVBlock

map --mem /winvblock.img (fd1)

map --mem (md)0x6000+800 (fd0)

map /2003.vhd (hd0)

map /2003.iso (0xff)

map --hook

dd if=(fd1) of=(fd0) count=1

chainloader (0xff)



title Setup 2003 - 2nd (GUI)

map --mem /winvblock.img (fd1)

map --mem (md)0x6000+800 (fd0)

map /2003.vhd (hd0)

map 2003.iso (0xff)

map --hook

dd if=(fd1) of=(fd0) count=1

root (hd0,0)

chainloader /ntldr

WinVBlock I used is the one from this post

AND grldr is the one posted by karyonix in the present thread.

as you can see I have to use the twice floppy mapping (it's a problem with my bios 0602 on a asus p5q pro turbo)

previously I succeded into installing and booting 2003 using VBoot, as described here BUT that way doesn't support WINNT.SIF neither in 2003 or xp and setup is much SLOWER.

now I'm going to usb-trick the vhd and put it on my WD USB.

thanks a lot.

[edit: made a mistake into the code text]

Edited by davlak, 01 February 2011 - 04:03 PM.

[Vortex]

Hi davlak,

Thanks for your post. What's the HAL type of your computer? The issue happens when trying to install Server 2003 on ACPI Multiprocessor computers.

[Vortex]

Hi davlak,

The installation went fine but booting Server 2003, the BSOD appeared : PROCESS1_INITIALIZATION_FAILED and the error code 6B

System : ACPI Multiprocessor Computer

Edited by Vortex, 01 February 2011 - 07:21 PM.

[davlak]

Hi Vortex,

halmacpi.dll is running on my 2k3's VHD on USB.

I've booted it fine on 3 PC with different HW (though all INTEL) but I've a issue.
Whilst XP VHD can boot this way

map /xp.vhd (hd0)

map --hook

root (hd0,0)

chainloader /ntldr

win2k3 needs always:

map --mem /winvblock.img (fd0)

otherwise it reboots immediately at the first logo of windows server
(no BSOD).

and one more question: in device manager, both in winxp and win2k3 I've a unknown device and its driver is wvblk32.sys (winvblock)
drivers are correctly installed and registry key are ok...
need help, thanks in advance.

[Vortex]

win2k3 needs always:

map --mem /winvblock.img (fd0)

Hi davlak,

Many many thanks for your suggestion. It worked on my ACPI Multiprocessor HAL :

title Server 2003



map --mem /winvblock.ima (fd0)



map /Srv2003.img (hd0)



map --hook



root (hd0,0)

chainloader /ntldr

To verify the occurence of BSOD, you need to hit F8 when Server 2003 starts booting and then select :

Disable automatic restart on system failure

Your system ( and mine ) reboots if winvblock is not mapped into memory and you cannot identify the error message ( BSOD ) without disabling automatic restart.

In my system, a removeable driver named B appeared and it contains all the winvblock files loaded by :

map --mem /winvblock.ima (fd0)

davlak, once again my thanks and I will continue to test your suggestion.

[Sha0]

...and one more question: in device manager, both in winxp and win2k3 I've a unknown device and its driver is wvblk32.sys (winvblock)
drivers are correctly installed and registry key are ok...
...

What version of WinVBlock? 0.0.1.8.DEV Jan-30-2011? If so, simply update the driver using the .INF file and it won't look so ugly. Or inject:

Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\root#winvblock]

"Service"="WinVBlock"

"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

And you will at least get the SCSI adapter icon.

[davlak]

What version of WinVBlock? 0.0.1.8.DEV Jan-30-2011? If so, simply update the driver using the .INF file and it won't look so ugly.

yes that is the version but...no way...immediately after updating the driver both xp and 2k3 reboot and never restart unless loading the hive offline and deleting reg key concerning WVBlk32.sys, then rebooting with:

map /winvblock.img

Or inject:

Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\root#winvblock]

"Service"="WinVBlock"

"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

And you will at least get the SCSI adapter icon.

at this point i wanted to inject but incredible to say, there's no CurrentControlSet key but only CurrentControlSet1 and CurrentControlSet2

Edited by davlak, 01 February 2011 - 11:53 PM.