I am new to the Ultimate Boot CD. Anyways from what I can tell when creating a Boot CD you use your Windows XP CD to create a basic bootable CD to load the different diagnostics and repair programs, correct?
What I could not find out in the FAQ or guides is when creating this boot CD will it only create files for the PC it was created or can it be used on most any other PC? I am curious since I have many computers in my house with different chipsets and processors that I would like one CD to use for repairs on any of the computers. I have Intel i845, Intel G965, nVidia nForce3, VIA and Sis chipsets and Pentium 4, Core 2, Athlon 64 and Mobile Sempron CPU's.
Would I have to make one CD for each computer or would the one CD cover all bases? I have Windows XP Home SP2 and Pro SP2 CD's.
A less important question is if I add drivers are they just added to a list of available drivers for using when booting. Since some computers have hardware like nVidia and ATI cards I would like the final boot cd to load the appropriate drivers when booting.
If one Boot CD can not be made to work on all computers are there other diagnostic packages similar to UBCD with nearly as full a set of diagnostic and repair programs designed for multi-computer environments.
Full Version: Newb creating boot iso
First....
Note.... to avoid confusion on what you are refering too..
UBCD - is a DOS based boot CD with utils to repair / recover computers
UBCD4Win - is a Windows based boot CD to also repair / recover computers and also can include UBCD with it...
So when talking about UBCD4Win please don't call it UBCD since that is another project
Now onto your questions... at least in part.
UBCD4Win will usually have the required drivers for most systems you run across but like anything... there are always exceptions and you won't know if your system you are testing is one of those until you try it. For most repair and diagnostics that a system needs done there are only 3 main drivers that should concern you the most... hard drive controller ( mass storage controller is the same thing ), network card and finally video being the least important. Since newer controller cards are being made all of the time and they usually require different drivers... it always takes time to get these integrated into the build.
You also mentioned 2 Intel chipsets that may ( or may not ) require that you make a special set of drivers for them. Intel didn't strickly follow the vesa standards in this area so the default vga driver may or may not give you 16b color or higher resolutions. Most of the time if you just increase the amount of video memory the system BIOS allocates to 8Mb or more it will resolve these issues but if it doesn't... then a special set needs made to address it.
Network card drivers are fairly easy to add... if your net card isn't supported you will normally just add the drivers to the [UBCD4Win]\drivers\NET folder ( look at the other drivers for examples ) ...
Hard drive controller issues are a bit more complex. While adding a driver to them can be done, its an advanced user type of operation. It's actually easier to submit a request at the Driverpacks.net forum to get assistance in that area.
Note.... to avoid confusion on what you are refering too..
UBCD - is a DOS based boot CD with utils to repair / recover computers
UBCD4Win - is a Windows based boot CD to also repair / recover computers and also can include UBCD with it...
So when talking about UBCD4Win please don't call it UBCD since that is another project
Now onto your questions... at least in part.
UBCD4Win will usually have the required drivers for most systems you run across but like anything... there are always exceptions and you won't know if your system you are testing is one of those until you try it. For most repair and diagnostics that a system needs done there are only 3 main drivers that should concern you the most... hard drive controller ( mass storage controller is the same thing ), network card and finally video being the least important. Since newer controller cards are being made all of the time and they usually require different drivers... it always takes time to get these integrated into the build.
You also mentioned 2 Intel chipsets that may ( or may not ) require that you make a special set of drivers for them. Intel didn't strickly follow the vesa standards in this area so the default vga driver may or may not give you 16b color or higher resolutions. Most of the time if you just increase the amount of video memory the system BIOS allocates to 8Mb or more it will resolve these issues but if it doesn't... then a special set needs made to address it.
Network card drivers are fairly easy to add... if your net card isn't supported you will normally just add the drivers to the [UBCD4Win]\drivers\NET folder ( look at the other drivers for examples ) ...
Hard drive controller issues are a bit more complex. While adding a driver to them can be done, its an advanced user type of operation. It's actually easier to submit a request at the Driverpacks.net forum to get assistance in that area.
QUOTE (rdsok @ Apr 17 2008, 06:25 PM) 
First....
Note.... to avoid confusion on what you are refering too..
UBCD - is a DOS based boot CD with utils to repair / recover computers
UBCD4Win - is a Windows based boot CD to also repair / recover computers and also can include UBCD with it...
So when talking about UBCD4Win please don't call it UBCD since that is another project
Now onto your questions... at least in part.
UBCD4Win will usually have the required drivers for most systems you run across but like anything... there are always exceptions and you won't know if your system you are testing is one of those until you try it. For most repair and diagnostics that a system needs done there are only 3 main drivers that should concern you the most... hard drive controller ( mass storage controller is the same thing ), network card and finally video being the least important. Since newer controller cards are being made all of the time and they usually require different drivers... it always takes time to get these integrated into the build.
You also mentioned 2 Intel chipsets that may ( or may not ) require that you make a special set of drivers for them. Intel didn't strickly follow the vesa standards in this area so the default vga driver may or may not give you 16b color or higher resolutions. Most of the time if you just increase the amount of video memory the system BIOS allocates to 8Mb or more it will resolve these issues but if it doesn't... then a special set needs made to address it.
Network card drivers are fairly easy to add... if your net card isn't supported you will normally just add the drivers to the [UBCD4Win]\drivers\NET folder ( look at the other drivers for examples ) ...
Hard drive controller issues are a bit more complex. While adding a driver to them can be done, its an advanced user type of operation. It's actually easier to submit a request at the Driverpacks.net forum to get assistance in that area.
Note.... to avoid confusion on what you are refering too..
UBCD - is a DOS based boot CD with utils to repair / recover computers
UBCD4Win - is a Windows based boot CD to also repair / recover computers and also can include UBCD with it...
So when talking about UBCD4Win please don't call it UBCD since that is another project
Now onto your questions... at least in part.
UBCD4Win will usually have the required drivers for most systems you run across but like anything... there are always exceptions and you won't know if your system you are testing is one of those until you try it. For most repair and diagnostics that a system needs done there are only 3 main drivers that should concern you the most... hard drive controller ( mass storage controller is the same thing ), network card and finally video being the least important. Since newer controller cards are being made all of the time and they usually require different drivers... it always takes time to get these integrated into the build.
You also mentioned 2 Intel chipsets that may ( or may not ) require that you make a special set of drivers for them. Intel didn't strickly follow the vesa standards in this area so the default vga driver may or may not give you 16b color or higher resolutions. Most of the time if you just increase the amount of video memory the system BIOS allocates to 8Mb or more it will resolve these issues but if it doesn't... then a special set needs made to address it.
Network card drivers are fairly easy to add... if your net card isn't supported you will normally just add the drivers to the [UBCD4Win]\drivers\NET folder ( look at the other drivers for examples ) ...
Hard drive controller issues are a bit more complex. While adding a driver to them can be done, its an advanced user type of operation. It's actually easier to submit a request at the Driverpacks.net forum to get assistance in that area.
Does the UBCD4win get all of the drivers off of the Windows XP Install CD?
Because I can boot into the installer on my Windows Install CD and install windows onto any of these computers so my CD will access any of the hard drive both IDE and SATA, except for my Core 2 Duo which is using SATA RAID requiring me to use a floppy disc to load the controllers driver, the install CD by default will only see individual SATA hard drives. As for video on all of them I get basic color, either 8bit or 16bit, and a resolution of 800x600 which is fine for me for running repairs. As for networking all of my computers get working Ethernet except my Core 2 Duo. All of my Desktops also use dedicated Video cards, Radeon and GeForce, only the Core 2 Duo has an integrated Intel GMA X3000 but that is disabled in the BIOS. So I suppose I would need to add drivers for an Intel ICH8DH southbridge and Intel 82566DC Ethernet controller. With the video if 800x600 is high enough to use the diagnostic programs that is fine for now, I could always create a disc later on with all of the video drivers for higher resolutions.
So based on your post I assume then that the Boot disc made my UBCD4win will be as universal as possible, with the drivers it has access to, and not only created with a driver set for the computer it was created upon? So if made the CD on my Athlon 64 it would not only work on computer that use the drivers my Athlon uses.
The project uses both the drivers that comes on the Windows CD as well as the ones I've already mentioned that are added to it.
RDSOK,
Thank you for answering my questions. I was low on CD's and did not want to burn a coaster nor go and buy more. Since it does get drivers from the Windows CD I think this will work fine for me. Now off to burn a UBCD4win disc.
Thank you for answering my questions. I was low on CD's and did not want to burn a coaster nor go and buy more. Since it does get drivers from the Windows CD I think this will work fine for me. Now off to burn a UBCD4win disc.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.