Jazkal

MHz, I've been meaning to convert all my v2.6 scripts over to v3, just haven't made the time to do it. One thing I think is missing from the script is a loop. That code looks like it will run through once and then exit. You want it to run through, and then check to see if there is another dialog that comes up. MC, I run this from a master script which is run from the RUN registry entry on first login desktop load. I wait for it to exit out (after multiple New Hardware Wizards come up), and then continue on from there.

I run it in the RUN section of the registry from my own custom master script, and then delete the entry right before I reboot the machine for the last time. To run it from a batch file, I think you have to use a WAIT command, not sure on that, haven't used batch as my master engine in a while. The autoit script basicly loops inside itself, because some of my machines have differing numbers of new hardware popup dialogs. And once it stops detecting the dialogs, it exits, and allows the rest of the script to continue.

I don't see that problem on my XP installs. But I do use an AutoIt script to get past those dialogs on 2003. This is my AutoIt 2.6 script for Windows 2003: BEGIN: Sleep, 5000 IfWinExist, Confirm File Replace, , Goto, CONFIRM IfWinExist, Found New Hardware Wizard, Cannot Install this Hardware, Goto, NOINSTALL IfWinExist, Found New Hardware Wizard, The wizard has finished, Goto, FINISHED IfWinExist, Found New Hardware Wizard, Completing the Found, Goto, QUICK IfWinExist, Found New Hardware Wizard, Welcome to, Goto, NORMAL Sleep, 10000 Goto, START START: IfWinExist, Confirm File Replace, , Goto, CONFIRM IfWinExist, Found New Hardware Wizard, Cannot Install this Hardware, Goto, NOINSTALL IfWinExist, Found New Hardware Wizard, The wizard has finished, Goto, FINISHED IfWinExist, Found New Hardware Wizard, Completing the Found, Goto, QUICK IfWinExist, Found New Hardware Wizard, Welcome to, Goto, NORMAL Goto, EXIT NORMAL: WinActivate, Found New Hardware Wizard WinWaitActive, Found New Hardware Wizard Send, !n Goto, BEGIN CONFIRM: WinActivate, Confirm File Replace WinWaitActive, Confirm File Replace Send, !a Goto, BEGIN FINISHED: WinWaitActive, Found New Hardware Wizard, The wizard has finished Send, {ENTER} Goto, BEGIN NOINSTALL: WinWaitActive, Found New Hardware Wizard, Cannot Install this Hardware Send, {TAB 2}{ENTER} Goto, BEGIN QUICK: WinActivate, Found New Hardware Wizard, Completing the Found WinWaitActive, Found New Hardware Wizard, Completing the Found Send, {ENTER} Goto, BEGIN EXIT: Exit I have not tested this on XP, it may have to be "tweaked".

I add my I386 source directory to my $OEM$\$1\ directory. It automatically copies the files over during install, and from some testing I did a while back (results posted on MSFN somewhere), it was quicker than using xcopy.

I use a modded XBox running XBox Media Center. It has full remote control access to my entire DVD collection (which I have converted to high quality xvid) over the network. I know you can pick up used xboxes for under a $100 US, and a non-solder mod chip runs about $45 US.

I had the same problem. But I worked through it but doing a test install from the web. Grab these two folders: "extensions" - this one includes a folder named "{0538E3E3-7E9B-4d49-8831-A227C80A7AD3}" "forecastfox" - this includes a bunch of files and folders. And put them in the SOF "profile" folder. No rebuild your SOF package.

Ok, I figured it out. You have to add the "extensions\{0538E3E3-7E9B-4d49-8831-A227C80A7AD3}" folder to the profile as well.

Anyone else seeing this with FF1.5 and SOF? I've added the "forecastfox" folder to the SOF profile directory, and added the entries in prefs.js file. But I am still getting the two error messages.

2.0 is stand alone, but not sure if it is backwards compatible yet.

Haven't tried that one before nmX.Memnoch. I'll give that a try later. This is what I use, and it will install silently without rebooting: dotnetfx.exe /q:a /c:"install /l /q" Worked for my 32bit install. Haven't tested x64 yet, will get to that tomorrow.

hmmm You don't need to repackage it, unless I missed something, it will install silently without rebooting with this command: dotnetfx.exe /q:a /c:"install /l /q" Worked for my 32bit install. Haven't tested x64 yet, will get to that tomorrow.

This is an old known issue, and won't get fixed until the app vendors add those functions for x64.

Anyone know how to get around this, so I don't have to use the Servername in the login credentials?

Anyone have the x64 version of this?

Can someone tell me how to determine which one is which? Or is it just the standalone "amd64" entries that reference the txtsetup.sif? (meaning no preceeding or trailing "\")

we are trying to get Win2k3 SP1 (any flavor) working in a multi-boot (x86 and x64) DVD enviroment.

Thanks for the link. I have that version of the x86 version, but that link didn't provide an updated x64 version of the file.

Has anyone else had problems with devcon not working on x64 version of Winpe? I can't seem to get any output. I can run devcon, and it just doesn't do anything. No errors, and no output.

VMWare is on RC1 of v5.5, and it does x64 clients.

it was probably deleted because it is a "warez" release, and as such, is always deleted.

got an update. Microsoft has Broadcom 6.68.0.0 x64 drivers (very old) and they prevent the lockup. But even using these drivers, I still can't get the NIC's to pull a DHCP address. so, it continues

do you have the supporting DLL's installed and registered?

Yes, I tested it with and without the changes in the txtsetup.sif file, with the same results. I have a nice stack of coasters. I sure wish vmware would come out with a version that supported x64 clients

changing the entries in txtsetup.sif, didn't seem to matter at all. When I tried the 4-swap to 6dma4, I recieved the old: "NTLDR is corupt. The system cannot boot."

Tried that, didn't work. Same results.