IcemanND

Do any of the other users have admin rights? If so log in as them and reset the administrator password. Or if you really want to try and crack it you can try 'john the ripper' to try and crack it if you don't want to reset it and you didn't mae it too complicated.

if your windows installation is on the c: drive then you will do everything on C: Nakatomi is refering to a utility cd you can make and boot from to do the repair, if you have another machine you can make a cd on you could make a UBCD4windows.

I've tried the DP's to load the missing drivers to windows on an intel mac before Apple released boot camp without success. I think they may be similar harware but not have matching HWIDs.

As long as you have the cd it shouldn't be a problem, I've done it with every version of Xp available except Media Center, without a problem.

yep that's the lovely way to fix it. Have fun.

use too many resources

actually it would not shut down for 1 minute, plenty of time for the other commands to run. Net user aspnet /delete - deletes the user account aspnet

see: http://support.microsoft.com/default.aspx/kb/307545/en-us? You don't have to use the recovery console anything you have that will allow you to access your disk. Then follow the disk copy procedures.

what device are you trying to add the drivers for? Try this: Copy the driver files to c:\windows\inf\mydriver open registry go to HKLM\Software\Microsoft\Windows\CurrentVersion edit DevicePath key Currently it is probably %systemroot%\inf change it to %systemroot%\inf;%systemroot%\inf\mydriver Not sure if a reboot is required but it may be. Also if the driver has been installed before you want to remove the associated oemxx.inf from the windows\inf directory. either search for text in the file like the CAT file name or a driver file name or just delete all of them if you like. Now plug in the device and give it a shot.

BMSD only adds the ones that are part of the drivers from microsoft on the install cd. The rest have to be added to the list manually, which is why I use that script. Then Sysprep will add them to the image. So as long as you have all of the MSD added, and the other hardware dirvers available you should be able to drop one image on any machine with a matching HAL. for my images I create a folder at the root and put all of my drivers in it and then add the recursive path to the registry to them using the setdevicepath app found here so that windows has the drivers available during the pnp discovery. Then delete the folder and reset the registry key on the first reboot. You could also put it in the Sysprep folder so it is automatically removed if you want, then you just need to reset the registry key. HKLM\Software\Microsoft\CurrentVersion\DevicePath

-BMSD creates the MassStorageSection with the drivers that come with windows and any additional you add to the section yourself and adds them in so that they are seen at the first boot after syspreping. The other issue is which HAL is installed: From the other thread: http://www.msfn.org/board/index.php?showtopic=71121&hl=#

Yes, if all you need are a handful then just do those. Depending upon how many you add it can take as long as an hour for sysprep to install and create the mass storage drivers section. The image I am creating I need as many as possible since I'm trying to deploy it to any machine that may cross my desk. So far so good as long as it has the ACPI uni/multiprocessor HAL.

http://www.apple.com/macosx/bootcamp/ More and more people are buying and loving Macs. To make this choice simply irresistible, Apple will include technology in the next major release of Mac OS X, Leopard, that lets you install and run the Windows XP operating system on your Mac. Called Boot Camp (for now), you can download a public beta today. Hey, Bashrat - Think we should make a MAC DriverPack?

Why trim it down? If you sat through it creating the list you've waited through the longest part and the reboot will do the rest when deployed. If there are drivers there you don't want don't add the associated INF before you create the list

The Microsoft answer is no, and the sysprep answer is also no.The Microsoft supported method to do this is an in place upgrade or repair. Highly possible, I have not seen a system recently, since the Intel added HT to the P4 that wasn't an ACPI Uni/multiprocessor HAL. There is not a location that I know of to determine this. You could do clean install of Xp to the system and see what was loaded by the clean install.

Actually they can be compared, and they do get compared here frequently. Look at the end result. After the install is finished and after you ghost that finished install to a new machine you have the same thing. The question is how you want to go about depoying and how many you are doing.

Wow, I'm suprised you haven't been flamed yet. The majority of people here will tell you the only way to go is with a slipstreamed unattended install. Which is great if you are doing and install here and there. But if you are looking to deploy to a room full of systems or company wide, and you don't have a RIS server or equiv. setup, then ghost or equiv. is the way to go. I have done and still do both, it just depends upon the task. When building a training lab with 10+ computers and 18gb of software I use ghost. When loading a single users machine with 4 apps I use Unattended installs which I usually created manually but I have used nlite or hfslip in the past. If I could I would probably use RIS for the general user installs and use ghost for the mega installs. But since I have no RIS and can't convince the powers to be to deploy one I'm stuck.

Not that I have ever heard of. Why can't you preload the drivers?

oemsetup1.inf is one of the many Mass storage driver infs, in this case it is the inf for an AMCC 3ware 9000 Series SATA RAID Controller. This will be the full path to the driver INF for whatever MSD you are referencing with the HWID before the equal sign. EOF is End of File. Not required to be declared. Just causes it to exit the loop or call and return to it's called from location. You only need to do this if you are using the script I posted. When the script runs it creates a txt file named hwids.txt, and then appends this to the end of sysprep.hold into sysprep.inf.

If some of the machines you deploy to use HDD controllers that are not already part of the Windows driver package then, yes. But you could manually integrate more HDD controller drivers or use nLite to do it.

Add to sysprep.inf [sysprepMassStorage] HWID of MSD=INF Location PCI\VEN_13C1&DEV_1002&SUBSYS_100213C1=C:\DP\M\3\1\oemsetup1.inf And use the sysprep.exe command line you already have. I use the following CMD script to add the HWIDs I use from the MassStorage Driverpack. Change the directory path in the third line (Call :HWID c:\DP\M) to point to your directory subtree for MSDs Add [sysprepMassStorage] to the end of your sysprep.inf and rename it to sysprep.hold. setlocal enabledelayedexpansion Echo Creating MassStorageSection of Sysprep.inf Call :HWID c:\DP\M copy sysprep.hold /a +hwids.txt /a sysprep.inf GOTO EOF :HWID rem %1 is path to MassDriverPacks Folder IF "%1"=="" GOTO EOF IF NOT EXIST %1 GOTO EOF SETLOCAL ENABLEDELAYEDEXPANSION SET STDOUT=%cd%\HWIDS.TXT TYPE>%STDOUT% 2>NUL ::traverse drivers path CALL :TRAVERSAL %1 GOTO EOF :TRAVERSAL PUSHD %1 for /f %%f in ('Dir /b *.inf') do ( for /f "eol=- tokens=2 delims=," %%i in ('find /i "pci\ven" %%f') do ( for /f "tokens=*" %%j in ("%%i") do ( for /f "tokens=1* delims=_" %%k in ("%%j") do ( if /i "%%k" EQU "PCI\VEN" ( for /f "usebackq tokens=1* delims=; " %%a in ('%%j') do ( echo %%a=%cd%\%%f>>%STDOUT% ) ) ) ) ) ) FOR /F %%I IN ('DIR /AD /OGN /B') DO ( CALL :TRAVERSAL %CD%\%%I ) POPD GOTO EOF

No regedit will not let you know, unless you are importing a registry file. But I've yet to come up with a path string over 64000 characters. And I've put all of the driverpacks in c:\windows\inf\dp\.... without issue. UIU does not edit the INF files, those INF's are that way from the manufacturer which is why the folders are b_xxxxxx not Axxxx.

make a BartPE cd boot from it and return the file to its original location. If you don't have a machine you can make a bartpe cd on, then try a repair, or using the repair console.

try using the /ib command line swith with ghost it should capture the entire boot record.

If your converter has its own power connection check your bay and see if there is a connection on the back that is turned on/off by the switch that you could connect the conveter. That way when you turn the bay off it would turn the converter off.