I'm using UBCD 3.10 and the Win XP SP2 MSDN CD. After UBCD boots on the Dell Latitude D630, none of the chipset drivers work. I tried including these drivers in the ISO and installing them after the UBCD loads, but that didn't work.
What process should I use to get these chipset drivers to load with UBCD?
Thanks in advance,
Scott
Full Version: Dell Latitude D630 chipset problem
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
Ok.. on to the subject at hand... and to provide some background basics for a PE enviroment...
UBCD4Win ( as well as any PE based disk ) is designed as a diagnostic, repair and recovery CD. They are not meant to be a replacement OS nor do they require a complete set of drivers ( audio, motherboard chipset etc ) to perform those duties. Of course a PE enviroment can be extended into many other areas ( like audio for a quick example ) but these are outside the scope of the projects normal use.
So the important drivers are going to be the mass storage drivers, network drivers and video driver.... chipset drivers are really irrelevant then in that reguard since they aren't needed for accessing the hard drives, gaining network access ( to copy files to or from the network ), or being able to see more than just basic 640x480 16 colors since most applications need at least 800x600 and close to true color to work with them well.
So if you can access your hard drives.. access the internet or a network and have a decent video resolution and color... then UBCD4Win is working properly.
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
Ok.. on to the subject at hand... and to provide some background basics for a PE enviroment...
UBCD4Win ( as well as any PE based disk ) is designed as a diagnostic, repair and recovery CD. They are not meant to be a replacement OS nor do they require a complete set of drivers ( audio, motherboard chipset etc ) to perform those duties. Of course a PE enviroment can be extended into many other areas ( like audio for a quick example ) but these are outside the scope of the projects normal use.
So the important drivers are going to be the mass storage drivers, network drivers and video driver.... chipset drivers are really irrelevant then in that reguard since they aren't needed for accessing the hard drives, gaining network access ( to copy files to or from the network ), or being able to see more than just basic 640x480 16 colors since most applications need at least 800x600 and close to true color to work with them well.
So if you can access your hard drives.. access the internet or a network and have a decent video resolution and color... then UBCD4Win is working properly.
Hello Rdsok,
Thank you for your prompt response. I was getting access to my hard drive, NIC, and video, but thought there was a problem connecting to windows network shares. From the run prompt, I was putting \\ComputerIP to no avail. However, after reading your response, I just tried putting \\ComputerIP\ShareName and connected fine.
You were right, no need for any of the chipset drivers to work. Thanks for you help - you guys are doing a great job
Scott
Thank you for your prompt response. I was getting access to my hard drive, NIC, and video, but thought there was a problem connecting to windows network shares. From the run prompt, I was putting \\ComputerIP to no avail. However, after reading your response, I just tried putting \\ComputerIP\ShareName and connected fine.
You were right, no need for any of the chipset drivers to work. Thanks for you help - you guys are doing a great job
Scott
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.