Jito463

No, just the opposite Simon. SP1 still had the MS JVM, so they released SP1a to remove it so they could avoid the lawsuit.

Greetings. I've been kind of lurking here recently, helping out when I can, now I wonder if I could get some help myself. I've recently discovered this command that lets you centralize your $OEM$ directories for network installs, requiring only one instead of several: [unattended] OEMFilesPath="\\server\preinstall\generic" Where Generic would be the directory containing the $OEM$ directory. While I'm sure this works for a network install using WinPE, I'm trying to use it to combine them on my multi-boot DVD. Here is my current directory structure (using only XP Pro just to avoid wasting time): \ROOT |_1PPR (Pro Preinstall boot folder) |_1OPR (Pro OEM boot folder - non preinstall) |_Setup |___XPPro |_____OEM |_______$OEM$ (used strictly for SATA drivers) |_______i386 (etc, all other related directories included) |_____Preinstall |________$OEM$ (full preinstall directory) |________i386 (same as above) |___XPHome |_____OEM |_______$OEM$ (used strictly for SATA drivers) |________i386 (same as above) |_____Preinstall |________$OEM$ (full preinstall directory) |________i386 (same as above) The reason for having a split OEM and Preinstall directories is so I can use the same DVD to do a regular repair install or to do a preinstall (I don't want the $OEM$ directory parsed during a repair install). The downside is, I have multiple files now that aren't needed. My preferred directory structure: \ROOT |_1PPR |_1OPR |_Setup |___XPPro |_____i386 |___XPHome |_____i386 |___Preinstall |_____$OEM$ (full preinstall OEM Dir for all installs) |___OEM |_____$OEM$ (SATA drivers loading) This would benefit me two ways. 1) Only a single i386 directory taking up space on my DVD 2) Only one $OEM$ directory to make modifications to when I change my preinstall I've tried the following in my winnt.sif: [unattended] OEMFilesPath="\Setup\Preinstall" (from root of drive) [unattended] OEMFilesPath="..\Setup\Preinstall" (from boot dir, move up one folder then switch) [unattended] OEMFilesPath="%CurrentDrive%\Setup\Preinstall" (However, %CurrentDrive% wasn't a set variable) [unattended] OEMFilesPath="/Setup/Preinstall" (thinking maybe for local files it had to be /, worth a shot). So far, nothing has worked. I'll keep fiddling with it, but if anyone can make a suggestion that will get this working I would greatly appreciate it. Thanks for your time. I've also posted in the MS Preinstall newsgroup and waiting to hear back from there. If they post something before I hear from here, I'll let you guys know. I'm sure there are others who would find this equally useful. *EDIT* If I get this part working, I'll explain what I did to create batch files so I can create standalone iso's even with the directories stretched out like they are But it's a moot point if this doesn't work in the first place.

As others have said, if you have a legit copy of Windows, then call MS In the US, it's 1-425-635-3311. I don't know about other regions. I've had to send customers there before that had stupidly thrown away their COA with the product key on it (on OEM editions, it's on the outer wrapping). If you have a legit CD, they will ask you to prove it to them (they have ways) and then if you provie it they will provide you with a new key.

timezone="35" Remove the preceding 0.

I had a similar problem with TourP.exe every time. I just chalked it up to a bad disc. I don't think I did anything to fix it really. Have you tried reburning it, maybe at a slower speed or with different media?

Also, for these lines: Don't use the C:\, just use \. Setup automatically assumes the C drive.

Not to try and drag this conversation out any longer than it needs to, but while a sole DVD±RW drive is a good idea, it also has it's downsides. Number one, if you do a lot of CD burning, that puts extra wear-and-tear on your burner. Better to have a seperate CD-RW drive for that. What happens if one of the lasers fail (CD burning for example), but everything else works? Do you throw away the entire burner and buy a new one or do you add a CD-RW drive in and keep the DVD±RW drive a while longer? Not everything's so simple as you make it. If you don't want to make it designed to support multiple drives, that's your perogative. You made it and chose to post it however, so we also have the perogative of pointing out any potential flaws. Anyway, I've put in my $0.02 worth. I'm done.

Ah, yes. Forgot about WTools. That things bad enough it's almost a virus. You have to dig around pretty hard to get that one out.

Same situation here, Steel. I've installed it on both of my personal computers, all the work computers with XP (4 office, 3 demo) and all system builds are now going out the door with SP2 slipstreamed into the install. Also, any new machines that come in (providing they don't have a corp key on them, in which case we shove it real hard back at the customer ), gets an update to SP2 once we've removed any adware/spyware/viruses that could cause a problem on update. It's all working so far. Oh, and the list of apps that are "broken" by SP2 is only related to network connectivity. It's the firewall that "breaks" them. You just have to either open the ports needed or disable the built-in firewall and no breaking.

Firefox is good, and the fact that it's free is nice, but I've been a fan of Opera for a while now (since before Mozilla really got popular) and so I'm sticking with it for the time being.

And I have seen before (rarely, but it does happen) where the RAM modules can just go bad. Had a machine come in the other day that had worked before then it started erroring out and finally just stopped working. I pulled the RAM module out and got an error beep. Put one of our sticks in, and it worked. Put his stick back in, nothing. Put our stick back in again, and it worked. Go figure.

Personally I wouldn't need this, but say someone used it on a multi-boot DVD and the only DVD drive was the slave? That would be an example. I don't think Alanoll is being critical, he's just trying to help you out by showing you ways you can make it better.

A) Check your registry entries for the Fax installer ....HKEY_CURRENT_USER\Software\Microsoft\Windows\Current Version\(all Run keys) ....HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\(all Run keys) B) You can safely delete the desktop.ini. It's used to store preferences for individual folders (layout, etc). Don't worry about it. *EDIT* Darn emoticons!

I tell our customers that 256 is the BARE MINIMUM I recommend (we don't even sell less than 256MB sticks of RAM fortunately). Sadly, while I'm no Intel fan, we just built a 3.0GHz Socket-775 P4 with a mere FX5200 (though suitable for their purpose - old couple) and a single 256MB stick of RAM. *sigh* There's only so much you can do for them, then they just have to figure it out for themselves.

Have you tried putting a USB PCI card in the machine? Perhaps there's something wrong with your onboard ports. If that works, then you're looking at some sort of hardware issue (motherboard would be the most likely culprit).

A lot of it depends on the condition of the machines beforehand. Myself, I wiped and did a slipstreamed install of SP2 on my machine (but that was because a month prior I had installed from a slipstreamed SP2 RC2, heh. Bad idea since you have to uninstall RC2 to install the final build). However, all of the machines at work (5 at last count), plus all the customers machines that come in (after we clean up adware/spyware/viruses) were all upgraded to SP2 without incident.

I can't speak for 2005, but NAV 2004 was a definite resource hog. However, he said he's running 2003 which I've never known to cause that problem. However, I did just notice that he already mentioned Ad-Aware in his first post, I just looked right over the top of it, heh. Ah, well. Better to be overly cautious and help too much than to assume too much and not help enough.

Ack. I always shudder when I see the words USB and MODEM uttered in the same sentence. *shudders*

Have also tested here. Only just recently got around to adding my SP2 (pre)installs to my multi-boot disc, though. But they work fine. Note that on the link you provided, he specifically said: This doesn't mean you can't use the xp boot loader, just that you can't use setupldr.bin. Do it like Alanoll and the guide on flyakite.msfnhosting.com say, and it should work fine.

Do you have Alcohol software installed?

I usually use the xpboot loader to launch it, but you still have to edit the setupldr.bin file to point to the new boot directory if you use something other than i386 (which most people with multi-boot discs do).

In the Common Tasks window to the left, there is an option to "Hide the contents of this folder". If you do not have Common Tasks enabled, simply enable them, make the changes, then disable it again.

We've seen a few computer like that here at work. Running a virus scan from another computer and even doing a repair install usually fails to fix it. You'll likely just have to bite the bullet and format C: :/

Try scanning for adware/spyware. I usually use the two together as one often catches what the other does not. Ad-Aware SE and Spybot Search & Destroy 1.3

I don't believe you can rename the actual Administrator account. Any other Administrator-level account, yes. But there has to exist an actual account called Administrator if I'm not mistaken. I'm sure if I am, someone will point out my error. Btw, is this Home or Pro? Home I know for sure this is the problem. Pro, I'm not 100% certain.