MageJubi

@mgrande............After all that fuss and muss, it turned out my CPU was bad. (I even got a new mobo, memory, etc.)--It may have been my fault for letting it get up to 77c for a few moments. (but that's another story). It works fine in 32 bit. In 64 however, it was crash-city. All I got was the ever popular yellow error sign--at the slightest thing too-- i.e. the activation notice trying to start, etc. I yanked it out, and put in another new CPU--problem was gone, no errors. Everything loaded up just like it's suppose to. It was the CPU in my case...see if you can borrow one for a few minutes to test with.

I got that last error message about the "setup log files should contain more info". For me, copying the folders seperately (especially the I386 folder), solved the problem. For some reason, things got lost or corrupted when trying to copy everything at once. Have you checked all the folders/files on your XPCD to make sure they're identical in size to the originals?

Here's an Abcpy.ini for Adobe Photoshop Elements 4.0. Add your user info, and replace your setup.ini with this. Run "Adobe Photoshop Elements 4.0 msi /qn". Abcpy.ini

I used TrendMicro AV/FW for a long time, but as emails concerning a subscription renewal error never got answered, I looked elsewhere. I'm now using eTrust EZArmor by CA (they use ZoneAlarms firewall). It has AV, Anti Spam (which I'm quite happy with), and AntiSpyware in the package--(and it's free for Frontiernet customers). It loads right away, unlike TrendMicro, that often took a full 5 min to "initialize".

Autoit works fine, but I still wanted to figure out the switch route. This runs all the way through--even closing the reboot window...however, the "finish" window stays open. I tried various pskill, and nircmd lines to close it, but they won't run while it's still active. If we can close it, then this'll work fine. I've tried a ton of switch combos to no avail. The /qn and /qb switch "act" like they want to do something but go nowhere. The only combo that works at all is "/qr /norestart" . Putting /quiet, or /passive has negative results. I tried an "abcpy.ini"--it loaded the key ok, but no more. I also tried some of the "DisplayFinishDlg=NO", and "EnableFinishDlg.=NO, lines, but still can't close that pesky "Finish" window. Change your setup.ini as follows--add the /qr /norestart switch, and the two lines of customer info below...(run the program using the "Setup.exe" , not the .msi.--and no added switches). What do we need to kill that "Finish" window??. Is there a switch yet untried?, or is there a line that can be put in the .ini to do this? (setup.ini) [Launch] Count=1 Lang0=0009 Default=0009 EnableLangDlg=NO CommandLine0=msiexec /i "Adobe Photoshop Elements 4.0 (en_us).msi" /qr /norestart Silent=quiet [en_us] Title=Adobe Photoshop Elements 4.0 - Setup OSErrMsg=Your system does not support the minimum operating system requirement. Adobe Photoshop Elements 4.0 will only install on Windows XP or Media Center Edition 2005 Operating Systems. [CustomerInformation] Serial number: xxxx-xxxx-xxxx-xxxx-xxxx-xxxx

@MHz..I tried your WshSend script. (Thanks). The script ran fine--but the "c" still gets backspaced. Something glitchy somewhere. I'm going to dl the latest Auto-it beta, and also check out AutoMacroGen.

Hmmm. I tried ConrolSetText, and ControlSend. In both cases, the "c" gets backspaced, leaving "liense.key" Putting two "c's" in license isn't a biggie, as the script runs fine with them--but I'd still like to know what's causing the backspace of letters, or letters to switch from big to small cap.

I originally used Scite Scriptwriter for Crypto, but it didn't run the program properly later. (This has happened with another pg too). In the other case, the program's unlock key was all big caps--when I ran the script later, 80% of the letters got reduced to small cap, which gave an "invalid key" response. I deleted the line created by Scriptwriter, and typed it in straight--that worked fine. This has ocurred with both Scite 3.1.1.0 and 3.1.1.8 beta. I've found that sometimes a "ControlClick" had to be replaced with a "MouseMove", or "("{TAB}")" to make things work right. That doesn't seem right somehow, but I've only been tinkering with Auto-it and Scite for a couple weeks. (Auto-it noob ) I haven't tried ControlSend or ControlSetText yet.

I've been using Auto-it3 and Scite for about two weeks now (XP/sp2), and have had a lot of fun making scripts for some of my programs that already have silent switches--just to do it. I made one for Cryptoexpert 2005 PE last night (which works fine in Vm, and real world), and encountered an oddity that perhaps someone could explain. Part of the registration process asks for the path to the "license.key" which resides in the Crypto setup folder--below is a portion--notice in the pathway (C:\Install\Cryptoexpert\liccense.key) how I have two "c's" in license? For some odd reason, and during the execution of the script, "something" clicks behind the "c" and backspaces it, which effectively mispells the path. I then put two "c's"--one gets backspaced, leaving "license" spelled right. The script runs fine--I was just curious about what would make it backspace a "c". Thanks. WinWait("CryptoExpert 2005 PE") If Not WinActive("CryptoExpert 2005 PE") Then WinActivate("CryptoExpert 2005 PE") ControlClick("CryptoExpert 2005 PE" ,"Unlock" ,"Button4" ,2) Sleep(1000) WinWait("Registration","License file locatio") If Not WinActive("Registration","License file locatio") Then WinActivate("Registration","License file locatio") WinWaitActive("Registration","License file locatio") Send("C:\Install\Cryptoexpert\liccense.key") MouseMove(312,59) MouseDown("left") MouseUp("left") CryptoExpert.au3

WinTasks 5 Pro (Don't use spaces in your code--put numbers together) [attachment=9968:attachment]

Isobuster 1.8 (Looked here twice but didn't see it for 1.8, so delete if necessary) Tested on VMWare, and real world. (ISO, IMG, NRG boxes checked, no desktop or quicklaunch icon) [attachment=9955:attachment]

The script works fine. I added a couple lines at the end to take care of rebooting. (I downloaded both AU3 and sciTE--should've gotten these fine programs a long time ago )

Hey djsleepy...you might want to remove your key from the script I have Adobe PS4 also, and also am having trouble with it. Your script looks like it might do the trick--except I've never had the chance to work with Auto-it, and presently, don't know the first thing about it ....@ keytotime--I didn't see an ABCPY.ini file anywhere for this particular Adobe program--could one be made?. You see "Installshield", but it doesn't seem to produce a setup.iss file with the -r (-R) switch. It makes a temp folder in c:\ called "Config.Msi" which contains a .rbs file, but I don't see how it could be used.

Not sure about the Office Xp, but like Porn Loader said, as long as you haven't changed more than 3 components (video card, memory, etc.) you'll have no problem reactivating XP online . I format all the time and have zero problems reactivating. Have you tried Trend Micros online "housecall"?...Run it if you can access their site--it might take care of that trojan for you.

I gave up trying to load the drivers through my winnt.sif, and went through my ROE instead. I pulled the WHOLE audio folder off the MoBo's Cd and put it into my Install folder. Everything loads up completely on the second reboot--sound manager, the works. REG ADD %KEY%\034 /VE /D "Installing HDAudio" /f REG ADD %KEY%\034 /V 1 /D "%systemdrive%\Install\Audio\Realtek\Setup.exe -s" /f

Turns out, the CPU is bad--at least as far as installing/running x64...it still runs 32 bit stuff just fine--but I'm going to RMA it anyway. I changed the memory 3 times (Kingston, Crucial, Corsair all acted compatible), the mobo twice (an Asus P5WD2 premium the second time around), and then finally the CPU--a slight upgrade to 3.2g instead of 3.0g. The new processor loaded x64 without a single problem. Oh, and the bad CPU isn't a J series as I stated earlier, as it looks like they're 1mb cache, and these are 2mb--my mistake--too much latenight research Anyway, thanks a lot for the ideas and help.

Since a good number of people use VMware Workstation 5 to test unattended installs, app switches, etc., I thought I might mention something I ran across (at least in the final release 5.0.0.13124 ). After VM5 is installed, go to it's folder in "program files". I find a driver called "libeay32.dll"...so does Tenebrils' Spycatcher (almost 86,000 fingerprints in their database). It's listed spyware name is "RainbowCrack 1.01"--a password guesser. I isolated "libeay32.dll" on a floppy and ran a spyware check on just the floppy. Yep, it popped up as spyware. I deleted "libeay32.dll" from the VMware folder, and the program "seems" to work just fine without it. BTW, I bought and downloaded VM5 direct from VMware a month ago, and just redownloaded and installed the .exe an hour ago, with "libeay32.dll" again waiting for me. I also found that "smaller database" spyware tools such as the one in Trend Micro's Pccillin 2005, seem to miss it. Anyone else with a similar VM5 experience, or more info on "libeay32.dll"?

I tried the Kingston memory (that is on the Asus QVL), and---no change. Still get the error messages. That's OK...try some new components like the CPU or mobo here in another week or so...at least I've already got the extra memory for it.

That's a kick...I was at the Asus site looking at different memory, and noticed the Crucial DDR2 533 was no longer in the memory QVL--(the Ballistix is still there). Crucial still list both 256 and 512 as compatible with my mobo. I sent off for a couple sticks of Kingston--that is on the Asus QVL. If that works, then fine--if not, I'll try changing something else.

Asus list the Crucial 256mb module, while Crucial list both 265mb and the 512mb modules for this model motherboard--and Crucial guarantees both of those particular modules to work with this particular motherboard--or your money back. Hopefully, I'll get a few more components in a couple weeks or so--start changing parts around, and see what's causing the problem.

Well, I tried everything I could think of, including the ideas of PyrO and others to no avail. I spent a good bit of time at Microsoft support looking over error codes...most point to a mobo bios problem and simply say to update it--which is what I did when the problem first occured. The mobo works most excellent with XP Home in it, so for the time being, it looks like I'll have to "try and get along" with being able to use Alcohol 120%, TrendMicro, and all my "right click menu" programs again.

Interesting...I too notice some irregularities with the error message. It always triggers when the activation icon pops up--but at other odd times too...earlier, it went about an hour with no problem. I loaded VMware5, and Win2000 into that--no error messages. I have a ton of mobo's, but unfortunately not an extra DDR2 to test with. Voltage is good (and yes the plug is in). I do have another pci-x video card I could try--I'll try an IDE drive too. I went to Crucial (before I got the memory), where that model mobo is listed, and they "guarantee this particular memory will work with is mobo". I'm using the "buggy" machine right now--no errors except the one when the activation icon first popped up...I don't want to activate it until I find the problem and know all the components are stable.

PyrO, the full mobo listing is : Asus P5AD2-E Deluxe with Intel 925XE chipset...the processor is a P4 775socket 3.0g 630 J series (64bit/2mb cache)...the power supply is an Antec 550 "true" power...and I'm using a brand new "right out of the package" Win64 OEM cd straight from Newegg.com...There are no peripherals or anything else hooked up.

Thanks for getting back to me. I've been trying to find some more info....I'm using "final" version 5.2.3790.1830. No overclocking, no frills. I have 4 sticks of Crucial 512, all tested with memtest86...I did try it with just 2 sticks, but it didn't matter. The drive is a formatted single sata Maxtor. The error starts at 34--it'll still load if you leave the message as is...if you do click "ok" on it, the error reappears. During the loading, the error has a red/white x icon--eventlog description as follows: Source: WMIxWDM Category: none Event ID: 120 "Machine Check Event reported is a fatal memory hierarchy error Transaction Type 2 Memeory Hierarchy Level 1 Request Type 8 Address: 1034389248" After x64 is loaded, I get an error message with the yellow icon w/ exclamation point--description as follows: (*note that this error pops up about every 3-4 min) Source: WMIxWDM Category: none Event ID: 106 "Machine Check Event reported is a corrected error For more information, see Help and Support Center"......which takes me to a support page with the previous info except they list another entry as follows: "Symbolic Name: MCA_WARNING_UNKNOWN_NO_CPU" Hmmm...that CPU cranked out UT2004 earler in the day when I had XP Home installed, and without any hiccups, so I'm a bit confused with this one.

While installing x64, I get an error message at the 34 minute mark stating there is a "Machine Check Error". It always happens at the same point. The install will finish, but the problems remains. The error ID # is 120, and the source is: "WMIxWDM". According to MS, they have no more info at this time concerning this error message. I've got the system stripped down to the bare essentials. I'm running an Asus P5AD2ED with the latest bios, 2 gigs of Crucial, an Asus EN6800GT, and a Maxtor drive. I've doubled checked the bios settings. The system is new, and was tested with an XP home unattended cd a couple days ago, which loaded fine. UT2004 was played hard for quite awhile just to load the sytem down--CPU only got to 109f, and the memory modules were barely warm to the touch. Has anyone else experienced this glitch? (and I'm sorry if this question is already posted, as I did look first).