SINGLE IMAGE PROBLEMS

  • Thread starter Thread starter Guardian
  • Start date Start date
G

Guardian

I am building a single image to use on my all dell network (Laptops
and desktops). I am creating the image on Microsoft Virtual Machine
2007. Once everything is installed (software) I add my drivers and
then push it up to the server using ghost. When adding the image to
the Optiplex 755 It goes into an endless loop or restarts. The only
thing I can think of that would cause this is the SATA hard drive.
Any one have any thoughts or had this problem?

My install Notes/Instructions are shown below in a basic nutshell:

Step 1.) Install windows onto your starting PC (Virtual PC 2007)

Step 2.) Check device manager for drivers not installed by windows
(NOTE: DO THIS ON ALL PC MODELS THAT THE IMAGE WILL BE USED ON)

Step 3.) Once you have identified the drivers, download them and
expand the files... Dell places them in the C:\dell\R98765 naming
convention by default. Otherwise use Winrar to uncompress the
drivers.

Step 4.) Move these "R" folders into c:\windows\drv so that the folder
structure looks like: c:\windows\drv\R12345... etc... You can remove any
sub folders from the drivers' individual folders that indicate a
different OS win98, win95, winnt (if there is a winxp exclusively)...
This minimizes image size and path size making image load quicker.

Step 6.) Create a sub folder under the windows directory and call it
i386 ("c:\windows\i386") then copy the contests of your CD's i386
directory into it. (MAKE SURE ALL CONTENTS ARE COPIED)

Step 7.) Copy the "sysprep" directory to the root of the drive... "c:
\sysprep".

Step 8.) Move completed SYSPREP.INF to the sysprep folder or create a
new one with the setup manager wizard.

Step 9.) Run oempath.exe from command prompted and have it pointing
to driver directory. (Example: oempath c:\windows\drv) (The maximum
length in Windows XP is 4096... This is your only limitation with
drivers.)

(NOTE)There is an output txt file and also a registry file. You can
use the registry file to test future builds and driver adds and the
txt file is used for the ability to see what has been done.

Step 10.) Run Registry editing Script provided by Administrator (

(Registry Update Shown Below:)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]

"SourcePath"="c:\\windows"

"ServicePackSourcePath"="c:\\windows"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]

"SourcePath"="c:\\windows\\i386"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
\winlogon]

"LogonType"="0"


Step 11.) Finally, the following entries MUST appear at the end of
sysprep.inf:
(These are critical for you to get sysprep to look at all Mass Storage
Drivers)

[Sysprep]

BuildMassStorageSection=Yes

[SysprepMassStorage]

Step 12.) Execute sysprep (This will take some time!)



PLEASE HELP!

Thanks,

Guardian
 
It wouldn't be the SATA drive itself, but probably the drive controller, you
may need to add the drivers for it to your image.

--

----
Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question http://support.microsoft.com/kb/555375
_________________________________________________________________________________


Guardian said:
I am building a single image to use on my all dell network (Laptops
and desktops). I am creating the image on Microsoft Virtual Machine
2007. Once everything is installed (software) I add my drivers and
then push it up to the server using ghost. When adding the image to
the Optiplex 755 It goes into an endless loop or restarts. The only
thing I can think of that would cause this is the SATA hard drive.
Any one have any thoughts or had this problem?

My install Notes/Instructions are shown below in a basic nutshell:

Step 1.) Install windows onto your starting PC (Virtual PC 2007)

Step 2.) Check device manager for drivers not installed by windows
(NOTE: DO THIS ON ALL PC MODELS THAT THE IMAGE WILL BE USED ON)

Step 3.) Once you have identified the drivers, download them and
expand the files... Dell places them in the C:\dell\R98765 naming
convention by default. Otherwise use Winrar to uncompress the
drivers.

Step 4.) Move these "R" folders into c:\windows\drv so that the folder
structure looks like: c:\windows\drv\R12345... etc... You can remove any
sub folders from the drivers' individual folders that indicate a
different OS win98, win95, winnt (if there is a winxp exclusively)...
This minimizes image size and path size making image load quicker.

Step 6.) Create a sub folder under the windows directory and call it
i386 ("c:\windows\i386") then copy the contests of your CD's i386
directory into it. (MAKE SURE ALL CONTENTS ARE COPIED)

Step 7.) Copy the "sysprep" directory to the root of the drive... "c:
\sysprep".

Step 8.) Move completed SYSPREP.INF to the sysprep folder or create a
new one with the setup manager wizard.

Step 9.) Run oempath.exe from command prompted and have it pointing
to driver directory. (Example: oempath c:\windows\drv) (The maximum
length in Windows XP is 4096... This is your only limitation with
drivers.)

(NOTE)There is an output txt file and also a registry file. You can
use the registry file to test future builds and driver adds and the
txt file is used for the ability to see what has been done.

Step 10.) Run Registry editing Script provided by Administrator (

(Registry Update Shown Below:)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]

"SourcePath"="c:\\windows"

"ServicePackSourcePath"="c:\\windows"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]

"SourcePath"="c:\\windows\\i386"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
\winlogon]

"LogonType"="0"


Step 11.) Finally, the following entries MUST appear at the end of
sysprep.inf:
(These are critical for you to get sysprep to look at all Mass Storage
Drivers)

[Sysprep]

BuildMassStorageSection=Yes

[SysprepMassStorage]

Step 12.) Execute sysprep (This will take some time!)



PLEASE HELP!

Thanks,

Guardian
 
Also check in the BIOS to see what mode the SATA interface is working in. If
it has a 'compatible mode' or 'legacy mode' use that in preference to 'native
mode' which has far more compatibility issues.
 
I know its not the physical drive but the driver its self and how it
is added. I have the driver added to the image but it is still not
working. I checked the bio sand have imaged the device with the bios
set to ACHI, ATA, and Legacy (These were the only 3 options) with no
success. Any other ideas? Thanks for the help so far.
 
Back
Top