Dwinks

Finally I found the problem, it was XPize and its stupid command prompt changing thing, so if you are having issues with BTS driver packs, and have Xpize installed, try removing it and BTS should work. Problem solved, topic closed.

If you put more than a paper thin layer of paste, you will make your processor run hotter, and from the sound of how you were thinking of applying it, if you did it that thick, you may well burn your processor up. You would be FAR FAR FAR better with no paste at all than with too much. Yes, you should be able to nearly see through the paste, and cover it in a paper thin layer from corner to corner of the IHS, well, nearly to the edges, stop just shy of them to prevent any from being smushed out the sides.

When I did a search for the files that the batch scripts are trying to call, they don't exist on my computer. Perhaps the latest base package left them out?

I have all the driver packs in the driverpacks folder, and all of them are the most recent off the BTS site, and still no luck. I followed the walkthrough before, and set up a WindowsXP home disc for my own use, and am now trying to get one set up at work, following the same steps, to get a XP Pro disc to use when I build up new computers. I am not sure why I am having so much trouble this time. Last time I did it, I just followed the steps and it just worked.

I just downloaded the latest driverpacks yesterday, and when I run BTS_DPs_Slipstreamer_V6011.cmd it tells me "Windows cannot find "CABfiles_M1.cmd"" when I choose method 1. When I do method 2, it says "the system cannot find the file specified" twice in the cmd window, and same for method 3. UpdateChecker_V6011.cmd gives me an error too, saying "windows cannot find "Get_update.cmd". I have redownloaded the the base files and had no better luck. I have everything in C:\BTS\ so its not a spaces issue either.

In short, as stated here before, there isn't any point in having an excessively large page file. Considering the fact that you are here, asking about this, I would assume that your level of expertise would exclude any need to have a memory dump in case of a crash. I may be wrong, and I don't mean to insult or sound brash, but I am just guessing that a memory dump would't be anything you would need. I also saw a listing of hardware specs under your first post, which listed 2x1gig of ram. If that is the system you are speaking about, I would recommend no more than about 1gig of page file. Unlike linux swap files, windows doesn't use its page file to store hibernation data, it uses a seperate hibernation file, so you dont need to have a page file larger than ram. If you have 2 gigs of ram, the page file will never get used, and if it does, it would only be due to a program having a memory leak, and in that case, your system will likely be on its way to crashing or at least needing rebooted, and that program not getting ran until the memory leak gets fixed. Just leave the page file alone, and if you have already changed it, change it to something reasonable like 768-1536mb or so, more will have absolutely no benefit and possibly be detrimental.