cluberti

The patch to bypass the check for RAM is winsetup.dll in this thread. And yes, it'll run on Virtual PC, just without any Aero. But it'll run like crap

I actually tried it in a VM just to see what would happen - explorer.exe on XP crashed right out of the gate, and even after getting it to run, it called exports in dll files on XP that did not exist (but do in vista versions of these .dlls). You'd have to replace the entire GUI (and you'd also have to be running IE7) to even have a chance of this working properly, would be my guess.

You could always run a network trace and see what gets sent where - just a suggestion. Note that I am running 3 different versions of Windows, and NONE of my boxes do this - perhaps you have an explorer shell extension loaded or an Internet Explorer activex or BHO with a global hook that is doing this? I don't think it's actually explorer.exe doing anything malicious.

If they've got Vista, you could just use the built-in ImageX functionality. You'll get there eventually .

Also, using an ntuser.man profile (rather than ntuser.dat) will lock out profile-specific changes as well (won't keep documents and files off of the disk, but should keep changes from sticking to the other things).

Already responded to your post here: http://www.msfn.org/board/index.php?showtopic=93546 Try to keep from double-posting questions.

If you patch winsetup and install, it'll install on 320MB of RAM, or 256MB in a VM. It removes the RAM check, although there are features of Vista (like Media Center) I wouldn't suggest running, even on 512MB of RAM.

I can't say yes for sure - you don't even know what virus you may or may not have. It's corny, but you might want to call 1-800-PC-SAFETY and open a free case with Microsoft security to clean that box of yours.

Well, I can think of one easy thing to try - 1-800-PCSAFETY. I know it's corny, but virus/malware cases are free at Microsoft for Windows users, and they've got some tools you can't get on the public internet that might fix this for you. Otherwise, you're going to need a null-modem cable, a free COM port, and some knowledge of the Windows debuggers to catch this. I can help you with the latter, but it isn't easy. The former is though, and it'll probably save you from having to rebuild (although once you DO clean your box, I'd suggest strongly that you do back up your data and rebuild - you can't ever trust a box to be clean once it's compromised until you do a very clean reinstall).

I've seen this before, and I'm not certain what causes it except that it always seems to work the second time around. You could consider putting in a pause via vbscript or something - I wrote something awhile back that did this (waited for the network and tried to map a drive). Even if it failed, I always installed via UNC path, and it would "fix" my network issues because it would always run first - meaning that whether or not it would fail sometimes on some machines, everything worked (it didn't affect the "working" machines, and it would be the "failure step" on the broken machines). Give it a try: Dim sTestPath Dim intCount Dim objNet Set objFSO = CreateObject("Scripting.FileSystemObject") Set objShell = CreateObject("WScript.Shell") Set objVolatileEnv = objShell.Environment("VOLATILE") Set objNet = CreateObject("Wscript.Network") ' An UNC path here that will be available when network connection is in place sTestPath = "\\server\share" sTestPath = "\\RISSERVER\reminst\Setup\English\Images\IMAGENAME\UNATTEND" intCount = 1 ' test on volatile environment variable to avoid running logon script ' if the user has already run the logon script. If Not objVolatileEnv("LogonScript") = "Done" Then Do Until objFSO.FolderExists(sTestPath) ' sleep 5 seconds WScript.Sleep 5000 intCount = intCount + 1 If intCount = 6 Then MsgBox "Unable to connect to network share for 1 minute. Please notify your network administrator." Exit Do End If Loop ' share/folder available on server now, so continue ' objnet.MapNetworkDrive "Z:", "\\RISSERVER\REMINST","True","DOMAIN\LoggedOnUser","password" End If

Outlook Express does not have this functionality built-in, so she must have had something 3rd party installed. Take a look and see what suits her: http://www.google.com/search?q=Outlook+Exp...amp;startPage=1

I have never heard of this before, unless McAfee is indeed picking up a virus. Make sure you have your box patched up to MS04-028 - XP SP2 is not affected, but other software might be: http://www.microsoft.com/athome/security/u..._jpeg_tool.mspx If you make sure all of your affected software (if any exists on your machine) is patched to the latest versions, and McAfee is at the latest update version (you're probably running an 8.0 version of McAfee), then two things: 1. You aren't vulnerable to MS04-028, so breathe easier! 2. Contact McAfee support so they can figure out what is triggering their software to see a vulnerability that you aren't impacted by - they may want a copy of a file that triggers it, so be ready to provide it to them; they can usually tell you if your file is infected, or if their engine has a bug or some other fault that caused this (hope it's the latter ).

Honestly, I do not know. I'm assuming you have a working DHCP server in your environment - most of the issues I read about were boot disk issues, so I'd start there assuming your DHCP server is working properly for you.

Try this: 1. Install the "Debugging Tools for Windows" from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx 2. Create the directory C:\websymbols 3. Create the "_NT_SYMBOL_PATH" System environment variable (not user!), and set it equal to: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols More information on the _NT_SYMBOL_PATH environment variable can be found at: 311503: Use the Microsoft Symbol Server to obtain debug symbol files http://support.microsoft.com/kb/311503/EN-US/ 4. Create the directory C:\adplus 5. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is "C:\Program Files\Debugging Tools for Windows" 6. Type the following command in the command prompt, then press ENTER: gflags 7. Click the "image file" tab 8. Type the application executable name of the application that is crashing, then press the TAB key 9. Click the "Show loader snaps" box, then click OK 10. Open the application that is crashing 11. Type the following command in the command prompt, then press ENTER: cscript adplus.vbs -crash -pn application.exe -o c:\adplus - (change application.exe to the application executable name of the application that is crashing) 12. Do not interfere with the minimized cdb.exe window that is opened, let it run minimized - it is the debugger, and closing it would stop our debug session. Now, try to crash the application - the next time it crashes, it should create at least one .dmp file in C:\adplus, as well as some logs - compress those, and we can tell you where to upload them for review. This should help us figure out why your application is crashing.

DST changes are not included in x64 SP2 - you'll still need to install 931836 or install the reg changes in 914387 and run the script listed there as well. Also, sysprep'ing a machine with the hotfix can fail as well, so if you plan on building an image and sysprep'ing it, the reg changes and script are much safer.

It sounds like it's quite possible that you have SP2 files on your SP1 box, causing SP2 not to install (especially if you've got a newer ntoskrnl on the box). What happens if you install with the /o /n switches?

I haven't used Ghost in forever, but it looks like you aren't alone in your problems: http://www.google.com/search?q=ghostcast+1...amp;startPage=1

Doing that disables the shell extension "shmedia.dll" from loading, which is the media file property extractor explorer shell extension (the .dll responsible for determining who owns that file, and how to display things like thumbnails for the files). By killing that reg key, you disable the ability for this to run, and it'll keep the .avi files from crashing explorer.

Proxy .pac files can be used as the autoconfiguration URL, or pushed via WPAD. I'm not a firefox user, but I know firefox supports autoconfig urls that contain .pac files (since it's not a firefox or IE thing, specifically), so this should work fine for both: http://wp.netscape.com/eng/mozilla/2.0/rel...proxy-live.html http://www.microsoft.com/technet/prodtechn...k.mspx?mfr=true http://www.microsoft.com/technet/prodtechn...s.mspx?mfr=true http://www.microsoft.com/mind/0599/faq/faq0599.asp http://java.sun.com/j2se/1.4.2/docs/guide/...xie_config.html

Try running a tracert to www.example.com.sg and see where you end up - sounds like a DNS issue...

I figured - I'd suggest autoruns instead, as it's much more thorough, and has more options.

That's actually an old hotfix, replaced by 927891.

Any particular reason you're using msconfig.exe? Wouldn't autoruns from sysinternals do the same thing (better)? Or do you want to troubleshoot msconfig.exe itself, maybe...

Pebkac in error form: "An error has occurred between the keyboard and the chair. Try removing the user before attempting the operation again."

That error can mean many things - however, when running an application, it almost always means a dll is not registered properly: decimal -2147319779 / hex 0x8002801d : TYPE_E_LIBNOTREGISTERED - Library not registered. I'd say you could enable loadersnaps on the binary that runs the application and then launch it via adplus, but it'll require a good bit of command-line, registry, and debugger expertise and the debugging tools for windows installed. If you're up for it, I can help - otherwise, I'd say the easiest thing to do would be to contact the application vendor and have them troubleshoot it for you (it's definitely an application problem). Also, what version of Windows are you running this on, and is that application written to run properly on that version of Windows?