UBCD4Win Forums > UBCD4Win over RIS (possible?)

paulf

Jul 5 2005, 06:08 PM

I have built UBCD4Win, and burned the ISO. Works great.

What would be AWESOME is if I could make it network bootable via RIS!

I tried this using the instructions found here: (for WinPE)
http://www.wug-nordic.net/articles/winpe_ris.htm

I get the image to load and see the "UBCD for Windows" splash screen/backdrop and get a mouse pointer, but thats it. It just sits there forever.

I noticed that when it is network booted, I dont get the "Windows XP" logo right before it loads. It goes straight from the black-n-white progress bar directly to UBCD4Win. So it looks like it is not loading the kernel.

Has anyone else played with this? It would be so cool if I could have this network bootable to our entire AD!

Thanks!
-Paul

paulf

Jul 7 2005, 01:00 PM

Anyone?

I have tried everything I can think of. I am able to load BartsPE over RIS no problem (a good walk through at: http://staff.stir.ac.uk/thomas.speirs/Bart-PE_RIS.htm). However the UBCD will not load.

I am able to get to the spash screen and mouse pointer but thats it. During the inital loading progress bar, it does not prompt to press F8 for additional drivers, nor does it display the WinXP logo. So it appears to be a config issue inside of txtsetup.sif. Perhaps something in the [SetupData] container maybe?

-Paul

dirkgently42

Jul 7 2005, 01:33 PM

Maybe thread will help?

paulf

Jul 7 2005, 02:19 PM

QUOTE(dirkgently42 @ Jul 7 2005, 12:33 PM)

Maybe thread will help?

Ah! Thanks!

I actually just got it to boot off of the network right after I posted that. It is working great except that it cant detect any network adapters. heh. Kind of funny since it booted of the network in the first place.

paulf

Jul 7 2005, 06:38 PM

I am now able to get it to boot from RIS.

Everything is working fine except for networking support.

On the same computer if I boot from the CD, it installs networking with no problems.

When network booting, and I try to enable networking support I keep getting "Unable to install Network adapters" or something similar. When trying to use the bartpe gui utility to detect network adapters, none are detected.

I noticed some data in the setupapi.log that seems to be related (below).

Any ideas?

CODE

Service Pack = 0.0
Suite = 0x0000
Product Type = 1
Architecture = x86
[2005/07/07 16:31:31 1204.2]
#-199 Executing "X:\i386\System32\AutoRamResizer.exe" with command line: AutoRamResizer.exe
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\UNKNOWN\9999".
#I296 DICS_ENABLE: Enabling device for profile (null).
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\UNKNOWN\9999".
#I300 DICS_DISABLE: Disabling device for profile (null).
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\UNKNOWN\9999".
#I300 DICS_DISABLE: Disabling device for profile (null).
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\UNKNOWN\9999".
#I296 DICS_ENABLE: Enabling device for profile (null).
[2005/07/07 16:31:49 1768.3]
#-198 Command line processed: X:\i386\system32\penetcfg.exe /UseProfile
#E412 Per-machine codesigning policy settings appear to have been tampered with. Error 2: The system cannot find the file specified.
#W413 Default of 1 restored to "Policy" value under HKEY_LOCAL_MACHINE\Software\Microsoft\Driver Signing.
#W415 Codesigning policy database re-synchronized to default values.
[2005/07/07 16:31:50 924.89]
#-198 Command line processed: "X:\i386\System32\bartpe.exe" -minint
#W241 Assuming all device classes are subject to driver signing policy.
[2005/07/07 16:31:50 924.88 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_10de&dev_002d&subsys_001e10de&rev_15,pci\ven_10de&dev_002d&subsys_001e10de,pci\ven_10de&dev_002d&cc_030000,pci\ven_10de&dev_002d&cc_0300
#-018 Searching for compatible ID(s): pci\ven_10de&dev_002d&rev_15,pci\ven_10de&dev_002d,pci\ven_10de&cc_030000,pci\ven_10de&cc_0300,pci\ven_10de,pci\cc_030000,pci\cc_0300
#-198 Command line processed: "X:\i386\System32\bartpe.exe" -minint
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e1000325.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e100a325.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e100ant5.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\e100b325.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\ixgb325.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\w29n51.INF, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\w70n501.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in X:\i386\inf\yk51x86.inf, using [STRINGS] instead.
#E394 Failed to commit INF cache to "X:\i386\inf\INFCACHE.0".
[2005/07/07 16:32:02 924.90 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_1106&dev_3059&subsys_a0021458&rev_60,pci\ven_1106&dev_3059&subsys_a0021458,pci\ven_1106&dev_3059&cc_040100,pci\ven_1106&dev_3059&cc_0401
#-018 Searching for compatible ID(s): pci\ven_1106&dev_3059&rev_60,pci\ven_1106&dev_3059,pci\ven_1106&cc_040100,pci\ven_1106&cc_0401,pci\ven_1106,pci\cc_040100,pci\cc_0401
#-198 Command line processed: "X:\i386\System32\bartpe.exe" -minint
#E394 Failed to commit INF cache to "X:\i386\inf\INFCACHE.0".

dirkgently42

Jul 7 2005, 07:42 PM

It seems that the link I provided has got you off to a good start.
It is the first link that google lists when you enter the text from your initial post: "network bootable via RIS".
There are other threads referenced within this one. Did you see the last entry concerning installed ram and the ramdrive?

Does your burned copy of UBCD4Win work "normally" on more than one PC outside of what you are trying to do with RIS?

Your request for help on this particular subject may interest some in this forum, but I think it would be more productive for you to post your subsequent question and logs in the thread I suggested (on the other website/forum). They should be able to help you better as they have more direct and recent experience with what you need and the problems specific to RIS.
For any other problems, please don't hesitate to post here!

You did install/extract the drivers download to the BartPE/drivers folder? Just checking, as you mentioned the dreaded "Unable to install Network adapters" error which I have seen quite a few times, neglecting to install the drivers to the proper directory... or not at all.
If you have correctly installed the "official" drivers and that doesn't seem to work, you might try the beta version---
http://www.ubcd4win.com/forum/index.php?showtopic=2388&hl=

Maybe thread will help? Hee, hee... typo!

paulf

Jul 8 2005, 03:20 PM

The CD works great on all of the computers I have tested it with. When trying to PXE boot those same computers and load the UBCD for windows image, that works great also except that it cannot install the network drivers.

One thing that interested me... When PXE booting, if I do not copy the drivers from i386/inf and i386/system32/drivers and place them directly in the root i386 folder then I get the error that the OS image does not contain the proper drivers for your network adapter.

When I DO copy the drivers directly into /i386, then the image loads perfectly. It just cannot enable network support.

All of the other apps work fine though.

Something wacky with either the way RIS loads the image or something funny in txtsetup.sif is my bet at this point.

-Paul

QUOTE(dirkgently42 @ Jul 7 2005, 06:42 PM)

It seems that the link I provided has got you off to a good start.
It is the first link that google lists when you enter the text from your initial post: "network bootable via RIS".
There are other threads referenced within this one. Did you see the last entry concerning installed ram and the ramdrive?

Does your burned copy of UBCD4Win work "normally" on more than one PC outside of what you are trying to do with RIS?

Your request for help on this particular subject may interest some in this forum, but I think it would be more productive for you to post your subsequent question and logs in the thread I suggested (on the other website/forum). They should be able to help you better as they have more direct and recent experience with what you need and the problems specific to RIS.
For any other problems, please don't hesitate to post here!

You did install/extract the drivers download to the BartPE/drivers folder? Just checking, as you mentioned the dreaded "Unable to install Network adapters" error which I have seen quite a few times, neglecting to install the drivers to the proper directory... or not at all.
If you have correctly installed the "official" drivers and that doesn't seem to work, you might try the beta version---
http://www.ubcd4win.com/forum/index.php?showtopic=2388&hl=

Maybe thread will help? Hee, hee... typo!

cray1000

Oct 31 2005, 07:45 PM

I am going a little crazy trying to get network boot to work...

First, should I use tftpd32 or RIS.... I dont care about network connectivity...

I have read all the 911 forum threads and various how tos but cant seem to get this straight.

Can someone please help me to boot off of RIS. I dont want to do anything intrusive and would prefer not to use freeware tftpd since its a production domain controller.

Thanks

hilander999

Oct 31 2005, 08:05 PM

QUOTE(cray1000 @ Oct 31 2005, 07:45 PM)

I have read all the 911 forum threads and various how tos but cant seem to get this straight.

Did you read this one...
http://www.911cd.net/forums//index.php?showtopic=11048&st=0

It's not exactly what you are asking for, but it stilll might have the answer you need.

Other relevant(?) threads...
http://xpe.collewijn.info/index.php?mp=tftpd_ris.php
http://staff.stir.ac.uk/thomas.speirs/Bart-PE_RIS.htm
http://www.911cd.net/forums//index.php?showtopic=7742
http://www.911cd.net/forums//index.php?sho...indpost&p=78393