Jump to content











Photo
- - - - -

Installing Server 2003 into an .img file with Firadisk or Winvblock


  • Please log in to reply
119 replies to this topic

#101 Vortex

Vortex

    Frequent Member

  • Advanced user
  • 232 posts

Posted 02 February 2011 - 06:04 AM

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


While editing an off-line registry, you should modify ControlSet001. The article is an old one but explains how control sets are stored in the registry :

Control sets are stored in the HKEY_LOCAL_MACHINE subtree, under the SYSTEM key. There may be several control sets depending on how often you change system settings or have problems with the settings you choose. A typical installation of Windows NT will contain four:
\ControlSet001
\ControlSet002
\CurrentControlSet
\Clone
ControlSet001 may be the last control set you booted with, while ControlSet002 could be what is known as the last known good control set, or the control set that last successfully booted Windows NT. The CurrentControlSet subkey is really a pointer to one of the ControlSetXXX keys.


http://support.micro...kb/100010/en-us

#102 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13752 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 February 2011 - 08:17 AM

While editing an off-line registry, you should modify ControlSet001.

Right :thumbsup: , BUT wrong! :cheers:

While editing an offline Registry you should:
  • Check key HKEY_LOCAL_MACHINE\SYSTEM\Select
  • Edit the whatever ControlSet00n is pointed to in that key as "Current"
And yes, it is "normally" ControlSet001 :cheers:, but it is not "engraved in stone".

:cheers:
Wonko

#103 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 02 February 2011 - 01:21 PM

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

D'oh! Were you using a persistent image or a RAM disk? That is confusing, indeed. Did you install with sc.exe or with the Add Hardware Wizard or devcon? What do you have under HKLM\SYSTEM\CurrentControlSet\Enum\Root\WinVBlock\ and HKLM\SYSTEM\CurrentControlSet\Enum\Root\SCSIADAPTER\ ? You should only have one or the other, but not both. Using sc.exe will produce a device under the former. Using the other methods will produce a device under both, and result in an Unknown Device in Device Manager. Was this what happened?

#104 davlak

davlak

    Frequent Member

  • Advanced user
  • 224 posts
  •  
    Italy

Posted 02 February 2011 - 02:38 PM

Hi Sha0

D'oh! Were you using a persistent image or a RAM disk?


persistent image

That is confusing, indeed. Did you install with sc.exe or with the Add Hardware Wizard or devcon?

I've tried either sc.exe and in this case as soon as I give net start winvblock xp\2k3 restarts and then dies (unless offline editing registry as said)
or Add Hardware Wizard with similar result but a BSOD 7b and, at bottom page, "winvblock alive"

by the way: "Injecting" the registry does not produce any affect into device manager: UNKNOWN DEVICE remains

(and What do you have under HKLM\SYSTEM\CurrentControlSet\Enum\Root\WinVBlock\ and HKLM\SYSTEM\CurrentControlSet\Enum\Root\SCSIADAPTER\ ?


I have the following:


HKEY_LOCAL_MACHINE\sys\ControlSet001\Enum\Root\wvblk32 


the above is a empty key [missin CurrentControlSet but I understood after wonko's and Vortex's explanation that's ok].
and


[HKEY_LOCAL_MACHINE\sys\ControlSet001\Enum\Root\SCSIADAPTER]



[HKEY_LOCAL_MACHINE\sys\ControlSet001\Enum\Root\SCSIADAPTER\0000]

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

"Class"="SCSIAdapter"

"ConfigFlags"=dword:00000004

"Driver"="{4D36E97B-E325-11CE-BFC1-08002BE10318}\\0001"

"Mfg"="WinVBlock"

"HardwareID"=hex(7):72,00,6f,00,6f,00,74,00,5c,00,77,00,69,00,6e,00,76,00,62,\

  00,6c,00,6f,00,63,00,6b,00,00,00,00,00

"CompatibleIDs"=hex(7):64,00,65,00,74,00,65,00,63,00,74,00,65,00,64,00,5c,00,\

  77,00,69,00,6e,00,76,00,62,00,6c,00,6f,00,63,00,6b,00,00,00,00,00



[HKEY_LOCAL_MACHINE\sys\ControlSet001\Enum\Root\SCSIADAPTER\0000\LogConf]


You should only have one or the other, but not both. Using sc.exe will produce a device under the former. Using the other methods will produce a device under both, and result in an Unknown Device in Device Manager. Was this what happened?


well, at this point I'm a little bit confused about the dozens of experiments I've tried. I'm gonna reproduce it to send a clear feedback for the last question :happy_dance:

Edited by davlak, 02 February 2011 - 02:40 PM.


#105 davlak

davlak

    Frequent Member

  • Advanced user
  • 224 posts
  •  
    Italy

Posted 02 February 2011 - 08:44 PM

Hi Sha0

this is the situation immediately after setup finished:

Windows XP


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\wvblk32]



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\wvblk32\0000]

"ConfigFlags"=dword:00000000

"Legacy"=dword:00000000

"DeviceReported"=dword:00000001

"Service"="wvblk32"

"CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\

  6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,77,00,76,00,62,00,6c,00,6b,\

  00,33,00,32,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,5c,00,\

  77,00,76,00,62,00,6c,00,6b,00,33,00,32,00,00,00,00,00

"Capabilities"=dword:00000000

"ParentIdPrefix"="1&c0ac9c8&0"

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

"Class"="Unknown"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\wvblk32\0000\LogConf]



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\wvblk32\0000\Control]

"ActiveService"="wvblk32"



the key:

HKLM\SYSTEM\CurrentControlSet\Enum\Root\SCSIADAPTER

is missing.
moreover:


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\wvblk32]



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\wvblk32\0000]

"ConfigFlags"=dword:00000000

"Legacy"=dword:00000000

"DeviceReported"=dword:00000001

"Service"="wvblk32"

"CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\

  6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,77,00,76,00,62,00,6c,00,6b,\

  00,33,00,32,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,5c,00,\

  77,00,76,00,62,00,6c,00,6b,00,33,00,32,00,00,00,00,00

"Capabilities"=dword:00000000

"ParentIdPrefix"="1&c0ac9c8&0"

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

"Class"="Unknown"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\wvblk32\0000\LogConf]




and:


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32]



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32\0000]

"ConfigFlags"=dword:00000000

"Legacy"=dword:00000000

"DeviceReported"=dword:00000001

"Service"="wvblk32"

"CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\

  6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,77,00,76,00,62,00,6c,00,6b,\

  00,33,00,32,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,5c,00,\

  77,00,76,00,62,00,6c,00,6b,00,33,00,32,00,00,00,00,00

"Capabilities"=dword:00000000

"ParentIdPrefix"="1&c0ac9c8&0"

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

"Class"="Unknown"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32\0000\LogConf]



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32\0000\Control]

"ActiveService"="wvblk32"




more:




[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32]



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32\0000]

"ConfigFlags"=dword:00000000

"Legacy"=dword:00000000

"DeviceReported"=dword:00000001

"Service"="wvblk32"

"CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\

  6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,77,00,76,00,62,00,6c,00,6b,\

  00,33,00,32,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,5c,00,\

  77,00,76,00,62,00,6c,00,6b,00,33,00,32,00,00,00,00,00

"Capabilities"=dword:00000000

"ParentIdPrefix"="1&c0ac9c8&0"

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

"Class"="Unknown"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32\0000\LogConf]



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\wvblk32\0000\Control]

"ActiveService"="wvblk32"




and again




[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\wvblk32]

"Type"=dword:00000001

"Start"=dword:00000000

"Group"="SCSI miniport"

"ErrorControl"=dword:00000001

"ImagePath"="system32\\drivers\\wvblk32.sys"

"PdoDone"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\wvblk32\Enum]

"0"="Root\\wvblk32\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001







[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\wvblk32]

"Type"=dword:00000001

"Start"=dword:00000000

"Group"="SCSI miniport"

"ErrorControl"=dword:00000001

"ImagePath"="system32\\drivers\\wvblk32.sys"

"PdoDone"=dword:00000001





[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wvblk32]

"Type"=dword:00000001

"Start"=dword:00000000

"Group"="SCSI miniport"

"ErrorControl"=dword:00000001

"ImagePath"="system32\\drivers\\wvblk32.sys"

"PdoDone"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wvblk32\Enum]

"0"="Root\\wvblk32\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

as soon I will post registry (offline, as win don't reboot) AFTER trying to install the driver via sc and\or .inf
thanks

#106 davlak

davlak

    Frequent Member

  • Advanced user
  • 224 posts
  •  
    Italy

Posted 02 February 2011 - 08:56 PM

the following are the keys after sc.exe (immediately after net start win rebooted irremediably)




[HKEY_LOCAL_MACHINE\sys\ControlSet001\Enum\Root\wvblk32]



[HKEY_LOCAL_MACHINE\sys\ControlSet001\Enum\Root\wvblk32\0000]

"ConfigFlags"=dword:00000000

"Legacy"=dword:00000000

"DeviceReported"=dword:00000001

"Service"="wvblk32"

"CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\

  6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,77,00,76,00,62,00,6c,00,6b,\

  00,33,00,32,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,5c,00,\

  77,00,76,00,62,00,6c,00,6b,00,33,00,32,00,00,00,00,00

"Capabilities"=dword:00000000

"ParentIdPrefix"="1&c0ac9c8&0"

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

"Class"="Unknown"

"Driver"="{4D36E97E-E325-11CE-BFC1-08002BE10318}\\0000"



[HKEY_LOCAL_MACHINE\sys\ControlSet001\Enum\Root\wvblk32\0000\LogConf]



[HKEY_LOCAL_MACHINE\sys\ControlSet001\Services\WinVBlock]

"Type"=dword:00000001

"Start"=dword:00000000

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\

  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,77,00,76,00,62,00,6c,00,6b,00,33,\

  00,32,00,2e,00,73,00,79,00,73,00,00,00

"Group"="SCSI miniport"



[HKEY_LOCAL_MACHINE\sys\ControlSet001\Services\WinVBlock\Security]

"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\

  00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\

  00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\

  05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\

  20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\

  00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\

  00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00



[HKEY_LOCAL_MACHINE\sys\ControlSet001\Services\wvblk32]

"Type"=dword:00000001

"Start"=dword:00000000

"Group"="SCSI miniport"

"ErrorControl"=dword:00000001

"ImagePath"="system32\\drivers\\wvblk32.sys"

"PdoDone"=dword:00000001



[HKEY_LOCAL_MACHINE\sys\ControlSet002\Enum\Root\wvblk32]



[HKEY_LOCAL_MACHINE\sys\ControlSet002\Enum\Root\wvblk32\0000]

"ConfigFlags"=dword:00000000

"Legacy"=dword:00000000

"DeviceReported"=dword:00000001

"Service"="wvblk32"

"CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\

  6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,77,00,76,00,62,00,6c,00,6b,\

  00,33,00,32,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,5c,00,\

  77,00,76,00,62,00,6c,00,6b,00,33,00,32,00,00,00,00,00

"Capabilities"=dword:00000000

"ParentIdPrefix"="1&c0ac9c8&0"

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

"Class"="Unknown"



[HKEY_LOCAL_MACHINE\sys\ControlSet002\Enum\Root\wvblk32\0000\LogConf]



[HKEY_LOCAL_MACHINE\sys\ControlSet002\Services\Eventlog\System\wvblk32]

"EventMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\

  00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\

  5c,00,49,00,6f,00,4c,00,6f,00,67,00,4d,00,73,00,67,00,2e,00,64,00,6c,00,6c,\

  00,00,00

"TypesSupported"=dword:00000007



[HKEY_LOCAL_MACHINE\sys\ControlSet002\Services\wvblk32]

"Type"=dword:00000001

"Start"=dword:00000000

"Group"="SCSI miniport"

"ErrorControl"=dword:00000001

"ImagePath"="system32\\drivers\\wvblk32.sys"

"PdoDone"=dword:00000001





#107 davlak

davlak

    Frequent Member

  • Advanced user
  • 224 posts
  •  
    Italy

Posted 02 February 2011 - 09:05 PM

Posted Image

in win2k3 same situation above, and registry keys before\after sc.exe

Edited by davlak, 02 February 2011 - 09:08 PM.


#108 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 02 February 2011 - 11:14 PM

...in win2k3 same situation above, and registry keys before\after sc.exe

Oops. Please re-read the ReadMe.txt file carefully. Your sc.exe command-line wasn't right. You should perform this before re-trying:

sc delete wvblk32

Good luck!

#109 davlak

davlak

    Frequent Member

  • Advanced user
  • 224 posts
  •  
    Italy

Posted 03 February 2011 - 09:39 PM

@Sha0

excuse me, there must be a misundertanding.
this is a copy and paste from your readme.txt


After starting each driver, you should use Device Manager or the Found

New Hardware wizard to update the drivers using the .INF files.  Please

do this for the WinVBlock driver before installing and starting the

AoE and HTTPDisk drivers.



To install the bus driver, do:



  sc create WinVBlock binPath= c:\windows\system32\drivers\wvblk32.sys type= kernel start= boot group= "SCSI miniport"

  net start winvblock




wehre is my mistake?
may you explain please=^?

#110 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 03 February 2011 - 09:49 PM

...wehre is my mistake?
may you explain please=^?

I'm afraid that you typed:

sc create wvblk32 binPath= c:\windows\system32\drivers\wvblk32.sys type= kernel start= boot group= "SCSI miniport"

Based on the Registry data that you've shared.

#111 davlak

davlak

    Frequent Member

  • Advanced user
  • 224 posts
  •  
    Italy

Posted 03 February 2011 - 11:29 PM

well, I swear I've repeated just few minutes ago all the setup and as you can see that name wvblk32 is already present immediately after finishing installation.
and I confirm the sc line I've used is the same in your readme.
this is really strange.
:cheers: ;)

#112 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 04 February 2011 - 12:35 AM

well, I swear I've repeated just few minutes ago all the setup and as you can see that name wvblk32 is already present immediately after finishing installation.
and I confirm the sc line I've used is the same in your readme.
this is really strange.
:cheers: ;)

If you really are doing

sc create WinVBlock ...

rather than

sc create wvblk32 ...

Then I apologize and am mistaken. On my system, sc creates the service name that I give it. I confirm with

reg query hklm\system\currentcontrolset\services\winvblock

I'm sorry if this doesn't seem to be working for you. Due to your problems, I added a -cmd install feature to winvblk.exe last night after work, but haven't yet published it as I was hoping to track down and fix the Windows 7 installation-to-image-file bug before publishing that development version, but oh well.

The syntax will [soon] be is:

winvblk -cmd install -service wvblk32

(See the updated ReadMe.txt for more details.

#113 davlak

davlak

    Frequent Member

  • Advanced user
  • 224 posts
  •  
    Italy

Posted 04 February 2011 - 06:33 AM

@ Sha0
you have really nothing to apologize of, I only must thank you for your job. asap I'll try again with the new driver and send a feedback.

#114 Vortex

Vortex

    Frequent Member

  • Advanced user
  • 232 posts

Posted 04 February 2011 - 01:33 PM

Hi Sha0,

Thanks for the new release of Winvblock. I was able install Server 2003 on my file-backed disc using your latest Winvblock.

#115 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13752 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 05 February 2011 - 05:37 PM

Just to add some confusion :mellow:.

@Sha0 & @karyonix


Besides being possibly a GUI alternative to sc.exe and/or net.exe and/or devcon :)
http://tools.sysprogs.org/srvman/

Features

Here is a list of SrvMan's key features:

  • Allows creating driver and Win32 services without restarting.
  • Supports both GUI and Command Line.
  • Supports all modern 32-bit and 64-bit versions of Windows
  • Allows running arbitrary Win32 applications as services.
  • Allows installing & running legacy driver services in a single command line call.

Maybe this is useful :w00t::
Command line for legacy driver testing?
http://tools.sysprog...n/cmdline.shtml

Testing legacy drivers

You can easily test your legacy driver by using the following command line:

srvman.exe run <driver.sys> [service name] [/copy:yes] [/overwrite:no] [/stopafter:<msec>]


This command creates (or overwrites) a service for a given legacy driver file and starts it. If you have specified the /copy:yes switch, the driver file will be copied to system32\drivers directory. If /overwrite:no is specified, DbgMan will return an error if the service (or the driver file in system32\drivers) already exists. If /after:<msec> is specified, the driver will be stopped msec milliseconds after successful start. You can use this switch to test driver load/unload cycle.


:cheers:
Wonko

#116 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 05 February 2011 - 06:26 PM

...Maybe this is useful :):...

Thanks, Wonko the Sane. I already added -cmd install -service <service> to winvblk.exe a couple of nights ago. At some point, I do need to remove a hard-coded file-path in it. :mellow: Ideally, WinVBlock could have a GUI front-end similar to VFD's fine interface.

#117 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13752 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 05 February 2011 - 06:30 PM

At some point, I do need to remove a hard-coded file-path in it. :) Ideally, WinVBlock could have a GUI front-end similar to VFD's fine interface.

Or a nice, fine command line interface (like VDK has) and on top of it a pseudo-GUI of some kind. :mellow:

:w00t:
Wonko

#118 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 05 February 2011 - 06:55 PM

Or a nice, fine command line interface (like VDK has) and on top of it a pseudo-GUI of some kind. ;)

What's wrong with winvblk.exe?

#119 jspeng

jspeng
  • Members
  • 1 posts
  •  
    China

Posted 13 June 2011 - 07:48 AM

Hi Sha0,

Greate thanks for your efforts and contributes. I use karyonix's patched grub4dos and Winvblock, make ramos for win2003 R2 x64 successfully, and setup xp and win2003 through ISO image normally.

However, when setup win2003 R2 X64, BSOD appear, the error message is:
File \WVBlk32.sys could not be loaded.
The error code is 22.

My menu.lst for grub4dos is here:
title Setup windows xp/2003 through ISO, OS Image file is named as win.iso
map --mem (hd0,0)/boot/winvblock.img.gz (fd1)
map --mem (md)0x6000+800 (fd0)
find --set-root /win.iso
map --mem /win.iso (0xff)
map --hook
dd if=(fd1) of=(fd0) count=1
chainloader (0xff)

I use the same image file winvblock.img.gz to run RamOS of win2003 X64, it is successfully. use it to setup win2003 x86 version, still successfuly. It seemed the winvblk.inf has errors when setup windows x64, because if I switch to firadisk 0.0.1.30 image, it is ok.

The contents of winvblock.img.gz is following:
WVBlk64.sys
WVBlk32.sys
WINVBLK.CAT
WinVBlk.INF
TXTSETUP.OEM

Since I am not familiar with INF format, would you please correct it? So we can run RamOS and setup windows, both for xp/2003 and both for x86/x64, just by using one single IMG file.

Thanks,

Edited by jspeng, 13 June 2011 - 07:50 AM.


#120 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 03 August 2011 - 06:55 PM

Greate thanks for your efforts and contributes.

I hope they're useful.

My menu.lst for grub4dos is here:


title Setup windows xp/2003 through ISO, OS Image file is named as win.iso 

map --mem (hd0,0)/boot/winvblock.img.gz (fd1)

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

find --set-root /win.iso

map --mem /win.iso (0xff)

map --hook

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

chainloader (0xff)

I don't understand the point of the two virtual floppy disks. Could you please try:
title Setup windows xp/2003 through ISO, OS Image file is named as win.iso
map --mem (hd0,0)/boot/winvblock.img.gz (fd0)
find --set-root /win.iso
map --mem /win.iso (0xa0)
map --hook
chainloader (0xa0)
[/code]




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users