Jito463

Make sure you have the following sections in your winnt.sif: I also add the following sections that I copied from a winbom.ini file, but it may not actually be necessary (it doesn't hurt anything either, though).

I read his post, and understand perfectly what he's saying. And I'm not saying he's wrong either, as I have no proof either way. What I was asking for was some evidence that proves his point, which he not only failed to provide but adamently refused to. I tend to question anyone that won't back up their claims.

Well, I just find it a little hard to believe that no one else has reported on this considering how long you say it's been a "problem". You would think by now that *someone* would have done a study on it. But since you refuse to provide any support for your claims, I guess we'll just leave it at that and go our merry ways.

Well, either way, it won't work.

Nice. I like how you side-step the issue. Of course no software is perfect and that some people are inevitably going to have issues. But I was asking you to point to articles or some sort of evidence that shows what you were stating above to be your "credibility stick". Has no one done any articles testing this problem to prove your point? I'm just asking for some white papers or at least some tests done by a reliable source. Do you have any links at all?

While that is true, it's more work to edit all the txtsetup.sif files than it is to simply copy some 0KB files to the root of your DVD, especially if - like me - you have a LOT of options on your DVD. For example, I have 11 different choices for OS installs and each one is done twice (once for regular setup and once for preinstall). That's 22 different times I'd have to edit the txtsetup.sif to modify those lines. It's just not worth it. Not a bad idea, just not good for everyone.

I stopped coming by for a while after the last time when we couldn't figure this out. I'm glad to see someone finally did get it working. Tested it at work with x64 and the preinstall worked without a hitch. Now we just need to figure out how to add Vista to the multi-boot DVDs. @geitonaki One thing I feel should be pointed out is that you don't need the AMD64 directory for x64. Just the $WIN_NT$.~BT folder that's created when you run the setup from within Windows as Incroyable Hulk posted earlier. You should update your batch files accordingly.

Can you backup your claims? Because without proof, your "credibility stick" is about as strong as a wet noodle. I've installed NOD32 across multiple systems (trial version as I work for a system builder), and have used it personally on both my home and work machine through 32-bit and 64-bit installs (and I do consider myself a "power-user" as you put it), and we also use it on almost all our machines at work. You so-called serious issues have never arisen for me on any of the aforementioned machines. Do you have any evidence to display or are you just trying to blow smoke up our USB ports?

Actually, there's a guy (not sure if he's affilliated with HP or not) offering "pre-beta" drivers for HP printers on PlanetAMD64.com. A lot of people are using them, and I've also tested them on my Deskjet 3650, and they worked. The list the OfficeJet 5500, so it should support your OfficeJet 5510. If you want to find out, there's a 120-day trial of x64 you can download direct from MS.

I install all my games to another drive, so yes you can install to another location under x64.

Do you want to just stop MSN Messenger from running or eliminate it complete? If you want to eliminate it (like I always do), use this batch file: RunDll32 advpack.dll,LaunchINFSection %windir%\INF\msmsgs.inf,BLC.Remove Bingo, no more MSN Messenger to bug you.

Well, I bought one copy from PlanetAMD64.com and the other copy I got through the trade-up program from MS. However, you can buy it from Newegg.com, we sell it at work and there are other online retailers that offer it for sale. Just do a froogle search for Windows XP x64.

I believe you need to modify the structure of your driver floppy. Vista no longer uses the txtsetup.oem file. Just copy the actual driver files (including the inf) over to the root of the floppy and try again.

@Link21 I think I have to agree with the rest of these posters. I'm not a big fan of 98/ME anymore myself (though 98SE was definitely the best of the 9x series), but you just seem to want to bash on them, not seek peoples opinions.

Well, that's simple enough: IPCONFIG PAUSE Bingo, you have a batch file to display your IP.

The "wand" allows you to save your user/pass for any website and when you visit that site you can simply press CTRL+ENTER to automatically insert said user/pass without having to type it in. All passwords are kept within an encrypted file and you can even set a master password you have to enter in order to use the wand. I'm sold on Opera, without a doubt. I've been using it since v6 and I wouldn't use anything else. I keep IE around for the occasional trip to WU or for the very rare site that doesn't work with Opera, but 99.99% of my internet browsing is done with Opera. Admittedly it's not free, but it seems more polished than FireFox, and to me that's worth paying for.

Erm, what do you mean you can't by XP x64 edition? It's been out since April. I've got two final copies running on my home and work machines. It's just not released to the retail market, you have to buy it OEM.

Have you read this post that was right below yours? Well, it was below yours until I posted this.

That's what I used for a "hack job" on one of my batch files while I tried to find a way to prevent it from running after sysprep (silly me, I forgot to include the sysprep,inf, heh). I just copied a file to the root of the drive during the preinstall and deleted it after resealing the machine for the customer. If it existed, the batch file ran and installed the applications. If it did not exist (after resealing), the batch file would simply exit.

I wonder if you could do that for XP Home, since normally Home Edition blocks you from using Administrator in normal mode (can only login in Safe Mode). I'll test it on Monday if I get a chance and let you know.

Interesting. I'll have to check this out if I can. I found a program called ResTuner that's supposed to be able to edit x64 resources in a future release this fall (according to their sales dept.), but no idea exactly when that's supposed to happen.

Well, I did find a way to do it. I used a batch file to run the program after extraction with the start /wait command, then delete the file and itself afterwards. And I used the RunHiddenConsole program available here on the forums to hide the batch file. Not as clean of a method, but since I already own a copy of WinRar it's cheaper than buying some other program. We were needing something similar at work on our demo computer to keep people from playing the games when we weren't the ones showing them off.

RDRAM = Rambus = NOT CHEAP. 128MB of Rambus at work costs $58 per stick. And Rambus must be installed in pairs. So $116 for 256MB of RAM. That's not cheap by a long shot.

Just when I thought the thread was dead.....it's baaaaaaaaaaack.

Did you download the x64 compatible drivers for your devices? Your 32-bit drivers will not work under x64 Windows.