Jump to content











Photo
- - - - -

WinvBlock failed with BSOD 0x7B


  • Please log in to reply
57 replies to this topic

#51 maanu

maanu

    Gold Member

  • Advanced user
  • 1134 posts
  •  
    Pakistan

Posted 30 January 2011 - 05:53 AM

You are absolutely correct. The SYSPREP.INF file's [SysprepMassStorage] section is used to populate the CriticalDeviceDatabase. If you are comfortable and familiar with using this method to create a nice CriticalDeviceDatabase for a variety of hardware IDs, then go for it. It just means having to endure Mini-Setup (or whatever choice you make). Otherwise, have a look at the CDDB. Have a look at the IDs found in an .INF file. You might notice that where IDs in an .INF file use a back-slash ('\'), IDs in the CDDB use an octothorpe ('#'). You might notice a ClassGUID in both CDDB sub-keys and in .INF files. You might notice Service values in the CDDB and you might notice AddService lines in an .INF file.


so it means i will have to prepare by hand all the inf files involve ???

Sorry. My image is small enough that I typically boot it as a RAM disk image, not as a GRUB4DOS sector-mapped image. I don't need any USB drivers. You can use wimb's "learning process": Boot the image as a RAM disk for the first time on a brand new model, install devices (that connect storage, such as USB host controllers) in Device Manager, then re-capture the image. Then you can boot the re-captured image as a sector-mapped disk the next time.


i think it is the best idea as of now . but isn;t the LEARNING process done AUTOMATICALLY as sector mapped image when booting ?

thats why we use EWF i guess , to DECIDE ourselves that what changes we want to save and what now .

another thing , that pagefile is driving me crazy , when i use 300 MB or so pagefile it is OK , i can use media player and stuff like this easily for long enough in " sector mapped image " . but when i dont use pagefile.sys at all , it keeps popping up " virtual memory is low " and bla bla bla .

just wondering how you would overcome this issue in your SMALL image .


also, i remember you posted a batch file a while ago , to SLIM the xp exactly as your image somewhere , which we got to use after booting from PE , it will copy the windows files to our new made image file directly .

also , tell me , can i BORROW the set of your inf files in order to make my image more universal ? ;) :)

#52 Sha0

Sha0

    WinVBlock Dev

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

Posted 30 January 2011 - 06:42 AM

so it means i will have to prepare by hand all the inf files involve ???

No... I meant that SysPrep.exe uses the [SysprepMassStorage] section to automatically populate entries into the CriticalDeviceDatabase. So you can use that method.

But yes... You can manually create CDDB entries based on the information you find in .INF files.

...but isn;t the LEARNING process done AUTOMATICALLY as sector mapped image when booting ?

I don't understand why you have "but" up above. What is the problem/goal/challenge you have in your mind that leads to "but"?

The learning process could perhaps be roughly described as "associating new device IDs with drivers and having those associations persist for next time, without manually making CDDB entries."

You can use the manual CDDB entry method. You can use the automatic learning method. You can use both methods. Or you can use neither m7bhod. :cheers:

thats why we use EWF i guess , to DECIDE ourselves that what changes we want to save and what now .

Except that I get the impression that a lot of people use Microsoft's Enhanced Write Filter without a license. :cheers: (Could be mistaken, obviously.)

But... What is your goal? I thought it was to put your image file on a USB disk and be able to boot it on a variety of hardware. All I am trying to suggest to you is that when you boot for the first time on a new model and Windows sees a brand new device like PCI\VEN_8086&DEV_27CC, that your image already knows to use USBEHCI.SYS (for example). If your image is not prepared, Windows does not know to use USBEHCI.SYS for the device... Then it cannot find any descendant device for that device, including the USB backing disk (for example).

another thing , that pagefile is driving me crazy , when i use 300 MB or so pagefile it is OK , i can use media player and stuff like this easily for long enough in " sector mapped image " . but when i dont use pagefile.sys at all , it keeps popping up " virtual memory is low " and bla bla bla .

Yup. Paging to USB is not really a good idea if you consider that performance will be poor and the USB disk will get worn out. Page to an internal HDD volume or buy lots of RAM. :(

just wondering how you would overcome this issue in your SMALL image .

My image is utilitarian. I don't use it for fun or for browsing the Internet. It is very stripped-down and doesn't require much memory. I would page to an internal HDD volume if I wanted to overcome memory limitations.

...also , tell me , can i BORROW the set of your inf files in order to make my image more universal ? ;) :)

I do not often use a "boot G4D sector-mapped disk from USB disk" scenario; sorry.

I do not have a special set of .INF files, actually. I boot the RAM disk on a new hardware model, install the storage adapters/controllers and wired NIC with Device Manager, then delete all OEM??.?NF files and INFCACHE.1 from C:\Windows\Inf\, then re-capture the live (running) RAM disk as an image file. I use another computer to download these drivers from the computer vendor's web-site, then put those on a USB stick and connect it to the target system running the RAM disk-booted Windows. This isn't the same as the goal of your original post.

#53 maanu

maanu

    Gold Member

  • Advanced user
  • 1134 posts
  •  
    Pakistan

Posted 30 January 2011 - 09:11 AM

No... I meant that SysPrep.exe uses the [SysprepMassStorage] section to automatically populate entries into the CriticalDeviceDatabase. So you can use that method.


i am not very faqmiliar with its command line usage///



I don't understand why you have "but" up above. What is the problem/goal/challenge you have in your mind that leads to "but"?


my goal is ,

1.prepare an usb img file.( DONE )
2.boot it on many low ram systems as " sector-mapped" with EWF enabled / ( DONE on 3 systems )
3. thus introducing different drivers and configurations to my img , since the changes are being dynamically written to it (this is debate able issue , since i doubt it now after your last post , THAT only ram-based booted img file will SAVE the new changes , which we can then RE-CAPTURE later . ( NOT sure about this )
4. SHIFT the img file to NEW usb drives for boot on DIFFERENT computers. ( NOT done yet )


Shao , thank you so much for your time .

#54 wimb

wimb

    Platinum Member

  • Developer
  • 2918 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 30 January 2011 - 09:19 AM

Here's just an example of how it might work, the first time running on a new model:

  • Windows: Hey, I'm running HALACPI.DLL + NTOSKRNL.EXE! I have found a device ID that needs driving: *PNP0C08. What do I drive it with?
    .......
    (Over-simplified.)

Thank you for your interesting description of the internal "communication" in booting Windows.
It helps a lot to understand how it works.
I think I will read this many times .....

;)

#55 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 30 January 2011 - 09:25 AM

Is this using /MININT or as a "full" Windows?

"Full" (actually very little of it).
You can see it as an (extremely experimental and currently NOT replicable) version of XPCLI:
http://reboot.pro/3717/

:cheers:
Wonko

#56 cdob

cdob

    Gold Member

  • Expert
  • 1460 posts

Posted 30 January 2011 - 01:11 PM

so it means i will have to prepare by hand all the inf files involve ???

Or use existing translations.

Which Hardware do you like to support?
Do you use the same machine, but new USB drive?
XP dosn't contain USB 3.0 drivers by default.

As for XP USB controller, hub and storage:
REGEDIT4



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0300]

"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

"Service"="usbuhci"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0310]

"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

"Service"="usbohci"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0320]

"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

"Service"="usbehci"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\usb#class_08]

"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

"Service"="USBSTOR"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#CLASS_09]

"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

"Service"="usbhub"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#ROOT_HUB]

"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

"Service"="usbhub"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#ROOT_HUB20]

"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

"Service"="usbhub"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\usbohci]

"DisplayName"="Microsoft USB Open Host Controller Miniport Driver"

"Group"="Boot Bus Extender"

"Tag"=dword:00000003

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

"ErrorControl"=dword:00000001

"Start"=dword:00000000

"Type"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\usbuhci]

"DisplayName"="Microsoft USB Universal Host Controller Miniport Driver"

"Group"="Boot Bus Extender"

"Tag"=dword:00000003

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

"ErrorControl"=dword:00000001

"Start"=dword:00000000

"Type"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\usbehci]

"DisplayName"="Microsoft USB 2.0 Enhanced Host Controller Miniport Driver"

"Group"="Boot Bus Extender"

"Tag"=dword:00000003

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

"ErrorControl"=dword:00000001

"Start"=dword:00000000

"Type"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\usbhub]

"DisplayName"="Microsoft USB Standard Hub Driver"

"Group"="System Bus Extender"

"Tag"=dword:00000002

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

"ErrorControl"=dword:00000001

"Start"=dword:00000000

"Type"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\usbstor]

"Start"=dword:00000000

"Tag"=dword:00000007

"Group"="System Bus Extender"

"Type"=dword:00000001

"ErrorControl"=dword:00000001

"ImagePath"="system32\\drivers\\usbstor.sys"
Does WinvBlock reuqire addional settings for new USB partitions?

As for XP mass storage drivers: txtsetup.oem describe requirements to load drivers early.
No need to process *.inf fully.

Some chipset mass storage examples:
http://www.msfn.org/...post__p__845633
http://www.msfn.org/...post__p__823780
http://www.msfn.org/...post__p__874231

REGEDIT4[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&cc_0104]"Service"="ahcix86""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&cc_0106]"Service"="ahcix86""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86]"Type"=dword:00000001"Start"=dword:00000000"ErrorControl"=dword:00000001"Tag"=dword:00000021"ImagePath"="system32\\drivers\\ahcix86.sys""Group"="SCSI Miniport"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\PnpInterface]"5"=dword:00000001[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_8086&CC_0104]"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}""Service"="iaStor"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_8086&CC_0106]"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}""Service"="iaStor"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor]"Type"=dword:00000001"Start"=dword:00000000"Group"="SCSI miniport""ErrorControl"=dword:00000001"ImagePath"="system32\\drivers\\iaStor.sys""tag"=dword:00000019"DisplayName"="Intel AHCI/RAID Controller"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters]"queuePriorityEnable"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_10DE&CC_0104]"Service"="nvgts""ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_10DE&CC_0106]"Service"="nvgts""ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvgts]"Type"=dword:00000001"Start"=dword:00000000"Group"="SCSI miniport""ErrorControl"=dword:00000001"ImagePath"="system32\\drivers\\nvgts.sys""DisplayName"="NVIDIA nForce Serial ATA Driver"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvgts\Parameters\PnpInterface]"5"=dword:0x00000001[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#NVIDIA__Raid_Disk________]"Service"="nvrd32""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#__NVIDIA_______Raid_Disk]"Service"="nvrd32""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#NVIDIA__Raid_Disk_20_____]"Service"="nvrd32""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#__NVIDIA____Raid_Disk_20]"Service"="nvrd32""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*_NVRAIDBUS]"Service"="nvrd32""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*NVRAIDBUS]"Service"="nvrd32""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*NVRAID20]"Service"="nvrd32""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvrd32]"Type"=dword:00000001"Start"=dword:00000000"Group"="System Bus Extender""ErrorControl"=dword:00000001"ImagePath"="system32\\drivers\\nvrd32.sys""DisplayName"="NVIDIA nForce RAID Driver"
Manufactuer generic HardwareIDs are used.
Drawback: manufacturer driver files support some devices only.
E.g. iastor.sys 10.1.0.1008 support ICH7 and up. ICH6 is not supported.

#57 maanu

maanu

    Gold Member

  • Advanced user
  • 1134 posts
  •  
    Pakistan

Posted 30 January 2011 - 05:59 PM

thanks a lot cdob for posting this .

i was reading your post here

http://www.911cd.net...pic=22473&st=37

you shared a CMD file , do we just run it FROM running windows , and it will ADD CDOB's along with the usbbootwatcher service ?

i suppose above mentioned CDOB's also can be copied to your batch file and so on .
??

thanks once again .

#58 cdob

cdob

    Gold Member

  • Expert
  • 1460 posts

Posted 30 January 2011 - 07:00 PM

i was reading your post here

This is another solution: boot XP and fix a offline XP.
PCIIDE and intelide is added too.

i suppose above mentioned

That's another case.
SYSTEM\CurrentControlSet goes to running XP.
Copy missing files yourself.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users