tguy

You can go ahead and purchase a 64-bit machine if you want and can afford it. It will run most all of the newer 32-bit software programs with no problems. You will not be able to take advantage of the real performance enhancements however until you upgrade the applications to a 64-bit program. Checkout www.planetamd64.com for a list of applications and other information on the 64-bit platform. Good luck with your decision.

Can you post your WINNT.SIF, CMDLINES.TXT and RUNONCEEX.CMD file contents so we can take a look at them? I use RunOnceEx with Windows 2000 all the time. It works just fine. Where is the RunOnceEx.cmd file in your directory structure? It should be in the root of the $OEM$ directory with the CMDLINES.TXT file. I call my RunOnceEx from CMDLINES.TXT. [Commands] .\RunOnceEx.cmd Hope this helps, look forward to seeing your file contents. Remember with the WINNT.SIF to remove the Product ID code and replace with Xs.

FYI - According to my sources at Microsoft R2 will not have a SBS version available.

Try replacing the Inputbox code with this: Set objArgs = WScript.Arguments Const ForReading = 1 Set objDictionary = CreateObject("Scripting.Dictionary") Set objFSO = CreateObject("Scripting.FileSystemObject") Set objTextFile = objFSO.OpenTextFile(objArgs(0), ForReading) i = 0 Do While objTextFile.AtEndOfStream <> True strNextLine = objTextFile.Readline objDictionary.Add i, strNextLine i = i + 1 Loop Then pipe the file name of your text file to the end of the script execution. For example. Users.vbs Users.txt

Does the portable hard drive appear inside the disk manager console? If so, you may just need to assign it a drive letter. If not, look at device manager and see if there are any unknown USB devices or USB devices etc. that are not installed correctly. If there are, then uninstall the device and reinstall with the appropriate drivers. I use portable USB drives on all my 2003 servers to put backup files on. Works like a champ! Good luck.

Drive repartitioning the drives into two equal parts with some disk partitioning utility, Partition Magic, diskpart.exe etc. Make the first partition active and install Media Center on it. When its done, try the install process again and select the second partition to install the other copy to. Should work. Good luck.

Pretty sure you would install DOS 6.22 first into its own partition, then just install Windows 3.0 and 3.11 into separate directories on that partition. You can start them each from within there own directory. As for Windows 95, just install that to its own drive partition on the same disk. That should do it. Good luck.

I would still suggest putting it in the $OEM$ folder then use cdimage.exe to create the .iso image. It has command line switches available that will create pointers to the first instance of a particular file for all subsequent copies of that file that it finds and will greatly reduce the amount of space used. Otherwise you can copy the files over with a batch file in the cmdlines.txt or GuiRunOnce or RunOnceEx it is up to you.

Francesco, It sounds like either your %PATH% variable may not be set right when wpi.hta runs or .hta files are not associated correctly. Check to see if the path is modified, run the PATH command from a dos or command prompt and see if %windir%\system32 is in the path. If it is, Windows should know to run mshta.exe with .hta files. Hope this helps.

You might want to check out passprop.exe with the /noadminlockout switch.

It is really not any different. I used the process for slipstreaming XP drivers on my 2K3 build and it works fine.

Try logging into the computer as <Computername>\Administrator instead of just administrator.

@joeadi2010 Your image was not attached to either of the posts I saw. Please edit your post and attach the image you want everyone to see.

Please do not cross post requests as the forum rules/guidelines suggest. If you post in the wrong forum one of the moderators can move the topic to the appropriate forum for you.

Generally speaking, there are command line options you can run along with the transform switch like /ENFORCELOCALCACHE etc. that may help you accomplish your goal. I found the switches in either the Office forum or on Google.

Not sure what file you are pointing Nero to but if you use a boot image file (w2kboot.bin, boot2k3.bin, boot.bin) etc. you can just include in the root of the directory structure (in the same folder as setup.exe) Then use the process outlined at unattended.msfn.org or use Nero to build an .ISO file that you can in turn burn to DVD. Hope this helps. If you can't find any of the above files, let me know and I can send you mine. Good luck.

I would suggest you pose this question in the Device Drivers section of this forum. Also, read the tutorial at http://unattended.msfn.org. There is a lot of info. on slipstreaming drivers.

SBS 2003 has its own SP1 separate from that of Server 2003 Ent. or Std. etc. You can download it from MS and it should integrate the way others do. Check it out and try it in a VM. Should not take up a lot of time.

You can use the netsh.exe tool, executed via a batch file like this: netsh interface set interface name="Local Area Connection" newname= "Prod"

You could use vbScripts to add users like this: '**************************************************************** Option Explicit ' On Error Resume Next Const UF_SCRIPT = &H1 Const UF_ACCOUNTDISABLE = &H2 Const UF_HOMEDIR_REQUIRED = &H8 Const UF_LOCKOUT = &H10 Const UF_PASSWD_NOTREQD = &H20 Const UF_PASSWD_CANT_CHANGE = &H40 Const UF_TEMP_DUPLICATE_ACCOUNT = &H100 Const UF_NORMAL_ACCOUNT = &H200 Const UF_INTERDOMAIN_TRUST_ACCOUNT = &H800 Const UF_WORKSTATION_TRUST_ACCOUNT = &H1000 Const UF_SERVER_TRUST_ACCOUNT = &H2000 Const UF_DONT_EXPIRE_PASSWD = &H10000 Const UF_MNS_LOGON_ACCOUNT = &H20000 Dim objComputer, objGroup, objUser, objWSHNetwork, ObjPwdExpires, strComputerName, strFullName, strPassword, strUserName Set objWSHNetwork = WScript.CreateObject("WScript.Network") strComputerName = objWSHNetwork.ComputerName Set objComputer = GetObject("WinNT://" & strComputerName) Set objGroup = GetObject("WinNT://" & strComputerName & "/Administrators") strUserName = "Emeruser" strFullName = "Emergency User" strPassword = "Password" Set objUser = objComputer.Create("User", strUserName) objUser.SetPassword strPassword objUser.FullName = strFullName objUser.Put "description", "Local User Account for Emergencies" ' WScript.Echo objUser.UserFlags objUser.Put "UserFlags", objUser.UserFlags Or UF_PASSWD_CANT_CHANGE objUser.Put "UserFlags", objUser.UserFlags Or UF_DONT_EXPIRE_PASSWD objUser.SetInfo '*** Add user to Administrators Group *** objGroup.Add "WinNT://" & strComputerName & "/" & strUserName objUser.SetInfo ' MsgBox "Completed adding user " & strUserName & ".", vbInformation, "Execution completed"

You could try installing it with the -u -z switches by executing it in the cmdlines.txt file. It is not integrated but it will execute. Rollup 1 and Rollup 2 should both work this way.

If you are worried about permissions you can use the GPO to elevate the privileges or use the 'RUNAS' function to elevate privileges while the batch file executes. You could also write a registry file and place the minus(-) sign in front of the key you want to delete and then execute it with regedit /s That should work no problem.

I use a vbScript I wrote to modify the file: Here is a copy of the script. ' Modify Boot.ini file attributes Set objFSO=CreateObject("Scripting.FileSystemObject") Set objFile=objFSO.GetFile("C:\boot.ini") If objFile.Attributes AND 2 Then objFile.Attributes=objFile.Attributes AND 0 End If 'Modify Boot.ini timing parameters Set TF=objFSO.OpenTextFile("C:\boot.ini",1) '1=ForReading inp=TF.ReadAll out=Replace(inp,"30","10") Set TF=objFSO.CreateTextFile("C:\boot.ini",True) TF.Writeline out TF.Close ' Set Boot.ini file attributes back to Hidden & System If Not objFile.Attributes AND 1 Then objFile.Attributes=objFile.Attributes XOR 2 objFile.Attributes=objFile.Attributes XOR 4 End If

You could also add the following key to the registry tweak for machine wide behavior: [HKEY_Local_Machine\Control Panel\Keyboard] "InitialKeyboardIndicators"="2"

Try generic 2 button mouse and standard 101 key keyboard and see if that does not work.