Jito463

It's got to be a static picture. I did it with Azureus loaded in the background downloading a file, and when I clicked Start -> Shut Down, the display in Azureus no longer updated. I waited a moment then clicked cancel. Azureus suddenly refreshed the display as if it had never stopped.

Not to deter from this site, but for support with finding x64 drivers you should check http://www.planetamd64.com. I've been a member there for a while as well and if there's a driver to be found they can help.

That method will cause the preinstall CD/DVD to stop functioning after a specified date, but will not affect any machines which have already been setup using that disc.

Try using %SrcDrv% instead of %SrcDir%.

I've been looking into renaming the $WIN_NT$.~BT section in setupldr.bin, but I'm stuck on something. Does anyone know what file references the $WIN_NT$.~LS directory? I can't seem to find any mention of it. It's got to be referenced somewhere, but where? I've looked in setupldr.bin, bootsect.dat, disk.sys, dmboot.sys, dmload.sys, ntfs.sys, ntdetect.com, txtsetup.sif, migrate.inf and ntdll.dll. I'm at a loss.

Did you highlight i386 before typing or just set the cursor in front of it? If you highighted it first, you would have removed part of the file instead of just overwriting it.

Well, i386\winnt32.exe is the setup program as I stated above.

Also NOD32. I've been using it for several months now. Works great for me.

Here's what I would suggest. On your desktop PC, put the CD in and run x:\i386\winnt32.exe /noreboot Where x:\ = the drive your XP disc is in. Follow the prompts and input the key you have for your laptop when prompted. Afterwards, you should have two new folders on your C: drive, $WIN_NT$.~BT and $WIN_NT$.~LS as well as a new file called $LDR$ (no file extension). Copy all of these files to your laptop hard drive along with ntdetect.com and ndldr. Now open your boot.ini on your C: drive and copy that to your laptop then remove the line that points to your Windows install (e.g. multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=alwaysoff /fastdetect) Afterwards, your boot.ini should look like this: Where "blah, blah" is whatever the text normally is. I can't remember right now. Theoretically, this should boot up and start the Windows setup as if you had initiated it from within Windows but doing a clean install. Good luck.

Actually, you made a minor mistake earlier (which I had already corrected once). Not a big deal, but with Deep Freeze you can specify portions of the HDD that do not get reset on reboot. So you can make and save documents with DF enabled that do not get erased when you restart the computer. I played around with it once for our demo computers at work. That way at the end of the day we could just reboot the computers and have everything back up and running like normal without worrying about customers messing them up. But the cost just wasn't worth it to us at the time, since after all they are just demo computers and a format/reload or reimage of the machine was far cheaper.

Something new I got to thinking about. In the setupldr.bin near the first listings of i386, there is a listing for $WIN_NT$.~BT (which is created when you run winnt32 /noreboot). I wonder if it's possible to use that to our advantage. Rename that listing instead of i386. Just thinking out loud. *EDIT* Just realized, I think that's what Viking was talking about above.

Hmm, seems to be a decent app. Much cheaper than Autoplay Media Studio as well. Worth looking into at least.

I doubt that.Maybe it just looks in registry for installion-path to its DLLs ? Because UltraISO also has something just like this, and it looks in registry for Nero DLLs to use while burning. And can you specify speed of burn? If u want a single-file solution to write CD/DVDs, then just like CDimage.exe, there is a cdburn.exe (by MS) as well. <{POST_SNAPBACK}> That's possible. I'll check on a machine without Nero installed to verify. As for speed, it burned at full speed (48x in this case), but with the --speed command you can control how fast or slow it burns. You can also use it to burn DVD's using the --dvd command.

What game is it? I've had luck doing that with a few games such as Farcry (though I still needed the original CD1 to play) and Painkiller Gold Edition. Knowing the name might make it easier to tell you if it's possible. Btw, this would probably have been better asked under the Software Hangout forum, isntead of the x64 Windows forum.

Well, I have a much simpler method of incorporating 2k3's memory management into XP. Run x64.

I usually recommend 1.5x your physical RAM. For example, I have 1GB of RAM, so I run mine min/max at 1536MB. Technically, anything over 1.5GB of RAM doesn't need a pagefile (though certain programs still require it's presence and Windows can't create a minidump without it).

censored disgusting patriotism <{POST_SNAPBACK}> What's disgusting about being a patriot?

Well, you could boot to a recovery console using your Windows disc and delete the page file. It will recreate itself on next reboot. Does the system seem unusually slow or is it just a larger page file than you're used to seeing? Also, I would *highly* recommend you upgrade your RAM. 256MB - especially if you play games like UT2k4 - is not nearly enough. Get up to 512MB at least, if not 1GB.

Attach your txtsetup.sif from your CD. Maybe something is corrupt in it.

Nero comes with a program I never knew about until recently called nerocmd. Attached below is the command-line parameters copied from (what else) the command-line help list. *EDIT* Just did a test and it worked great. Here's the command I used: <full path to nero>\nerocmd.exe --write --drivename <drive letter> --real --image <path to image> --underrun_prot You could also use this for command-line burning from the context menu (right-click, Burn with Nero). Just replace the --image <path to image> with: --image "%1" Ok, removed all the other edits. Here's the real deal. After putting the "full" path to nerocmd (in my case, D:\Program Files (x86)\Ahead\Nero\NeroCmd.exe) I got rid of the "Access Denied" message. Used the --image "%1" command and it burned perfectly. The disc is accessible and it closed itself out afterwards. It's good. The best part is, it seems to be self-contained. Meaning, I moved just NeroCmd.exe by itself to another drive and ran the same command-line using the single executable. It burned perfectly. I can think of a lot of uses for this. cdimage followed by nerocmd to burn an image after it's done. And that's just for starters. nerocmd.txt

Fortunately, I do have a x64 copy of WinPE. I'll play around with it a bit this weekend and see what I come up with. I love working for an OEM. I get such cool toys to play with.

Well, I finally got a chance to try modifying the ntldr. No go. Anyone else have any luck with this? I'm about to switch my setup over to a WinPE based method with CD installation. I'm sure that will work. But I really would like to continue using the current method instead.

Yeah, I didn't have access to my preinstall stuff at the time so I goofed the line. It was UnattendSwitch=Yes (not UnattendedSwitch=yes as you have it) that skips the user creation screen, not OemSkipWelcome=1. My bad.

Note that if you use the OemSkipWelcome=1 with XP Home, you may find yourself unable to login due to no users being created (with XP Pro you can login as Administrator, with XP Home you cannot). I found this out the hard way after setting up our preinstalls at work with this method. Not good.

Heck, I just added rarreg.key into my WinRAR SFX file and added the comments back in. Not setup for silent install, but it does copy my registration over during setup without a problem. *EDIT* I see sleepnmojo's link is pretty much the method I use each time a new version comes out.