Jito463

Both optical drives are IDE, so that shouldn't be an issue (I added the second one later, to test if the first was the problem). I did consider the bootfix.bin as the culprit, but didn't consider removing it from the image. However, given that it works on another PC, I can't imagine that being the case. It's just the standard bootfix for i386/AMD64, nothing has been modified. I've even used the same bin file for standard Windows XP discs (not x64). I appreciate the suggestion, though. I suppose I should mention a few specs, now that I think about it. The motherboard is a Gigabyte K8N Ultra-9. It has an Athlon X2 4400+ with 4 x 512MB Corsair XMS sticks. I've considered removing some of the memory, but I'm not getting any stability issues, so I doubt that it's related. However, I may test that later when I have a chance. *EDIT* On consideration, I just realized I could try a SATA DVD drive instead. When I have an opportunity to power down my primary PC, I'll pull the optical drive from it and test again. Still, if anyone has encountered this issue before, it would be helpful to hear your experiences with it. Even if you never did ultimately resolve the problem.

Ok, so I've got an unusual issue here. I've figured out a workaround, but I'm still curious to determine why this is happening, so as to prevent it from occurring in the future. Searches online yielded no results, save for what I had already determined myself. I'm attempting to reinstall XP Pro x64 on my backup computer. When I attempt to boot from the CD, it just skips that step and boots straight to the HDD. I've already made sure CD/DVD is the first boot device, and I've even taken the step of hitting F12 to choose the first boot device on startup. This isn't an issue with the DVD drive or the disc, as I've used 3 different discs on 3 different drives (including an external). I've also tested one of the discs on another laptop (just to make sure it would boot), and it did indeed begin the setup from the CD. So the discs are fine, and the drives are fine. I've tried using my current 36GB Raptor drive, and a test 40GB IDE drive I had laying around, the same situation occurs with both. However, if I completely wipe the 40GB (haven't tested yet with the Raptor, and don't want to until I'm sure everything else is working fine) - including all partition information - then the CD will boot without incident. I'm currently installing on the 40GB to make sure nothing is wrong with the system, before I proceed to wipe my main drive; but I was curious to find out if anyone else has encountered this issue and/or knows what the cause is and how to rectify it. It just dawned on me that I haven't tested with another version of Windows, but I doubt that would matter since I've already determined the discs work. Still, any insight would be appreciated.

I always lived by the rule that - when using a search engine - the more relevant information you type in, the more relevant information you get out. In this case, I guess I was just over-complicating things. Thanks for the heads up.

Just tested, and without /WAIT in my .cmd file, the programs all launched simultaneously. Added /WAIT, and the programs only ran one at a time. Sorry, but you're mistaken.

Some time back (and I believe I got them from here), I downloaded some tools to add expanding and compressing Windows files to the "Send To" Context Menu. There was a batch file version, and a VBS version. These worked great, all the way up to Windows Vista x64 (including through SP2). However, now I've moved on to Windows 7 x64, and I'm having some trouble. I can expand the files just fine, since Windows 7 has it's own Expand.exe built in. But ModifyPE.exe is no longer functioning. I get an error saying: ERROR - MODIFYPE CAN'T PATCH "filename.ext" Obviously, it does me no good to be able to expand a file, if I can't subsequently compress it again. I don't absolutely have to do this on my Win7 machine. I have two other machines, one with XP Pro and another with XP Pro x64, both of which would work fine to do the job, but it would be nice if I could do what I needed on all three of my systems. I've already disabled UAC, so that's out of the picture. Has anyone found a workaround, or possibly a better method of expanding and compressing Windows system files in Windows 7? I'm always game to try new methods, if it's an improvement over the old method. I tried searching the forums for "modifype windows 7", but found no relevant results. Any suggestions or advice would be appreciated, even if it's just to tell me that I'm out of luck, so I don't waste my time further.

I'd suggest not to use that syntax… IF ERRORLEVEL = n is first of all not correct Also an errorlevel of 0 means that errorlevel was 0 or greater which in all cases would be true. This would probably replace your command better IF EXIST "%PROGRAMFILES(X86)%" (GOTO 64BIT) ELSE (GOTO 32BIT) It's always worked for me, which is why I used it, but I will admit your version is much cleaner and will probably switch to that. By the way, in your version, the ( ) around the GOTO commands doesn't need to be there.

I've tried a number of different options, but I can't seem to make Opera install silently. In fact, when I try, it just launches like it's going to install, then stops doing anything. I've tried using the classic installer with /s, doesn't work. I've tried the regular installer with /s /s /v/qn /s /v/qn /V ALLUSERS=1 CREATE_DESKTOP_ICON=1 CREATE_QUICKLAUNCH_ICON=1 CREATE_STARTMENU_ICONS=1 MULTI_USER_SETTING=0 (also with 1) I've tried the MSI file from the regular installer with /qn /qn ALLUSERS=1 CREATE_DESKTOP_ICON=1 CREATE_QUICKLAUNCH_ICON=1 CREATE_STARTMENU_ICONS=1 MULTI_USER_SETTING=0 (also with 1) /passive /qn ALLUSERS=1 CREATE_DESKTOP_ICON=1 CREATE_QUICKLAUNCH_ICON=1 CREATE_STARTMENU_ICONS=1 MULTI_USER_SETTING=0 (also with 1) msiexec.exe /i <Opera_964.msi> /passive /qn ALLUSERS=1 CREATE_DESKTOP_ICON=1 CREATE_QUICKLAUNCH_ICON=1 CREATE_STARTMENU_ICONS=1 MULTI_USER_SETTING=0 (also with 1) None of these work. Any suggestions? Occassionally I have to reinstall Windows on a customer's machine, and I'd like to add Opera to my silent installs. I already have FireFox silent from another link here, but can't seem to get Opera to work. *EDIT* Bah, never mind. In my attempt to try many different options, I didn't bother to check between each attempt to see if anything was installed. It had got installed at some point, but didn't create any shortcuts. Going back to the classic installer with /s after making sure all traces were removed fixed the problem. Hopefully this will help someone else down the road.

I know this is an older post, but here's what I've always used: %ProgramFiles(x86)% IF ERRORLEVEL = 1 GOTO x64 IF ERRORLEVEL = 0 GOTO x86 If it exists (ERRORLEVEL = 1), then it runs the 64-bit (x64) commands If it does not exist (ERRORLEVEL = 0), then it runs the stanard 32-bit (x86) commands. Of course, you could do the same with SysWow64 instead. Just pick any file or folder that would only exist in a 64-bit OS.

Could it possibly be caused the the TCP/IP limits in Windows XP? If so, removing/increasing the TCP/IP limits might change that.

Hmm, it seems that upon further investigation, there is no way to stop WMP11 from syncing altogether. I'm still uncertain as to why it feels the need to constantly access my device, though. Especially considering that it's not even a media player.

Ok, got a bit of a unique problem. Then again, I can fix most issues, so it usually takes unique ones to get me to post. WMP11 has a nifty (though I would argue, annoying) feature of syncing to any USB device, even if it's not a media player. In this case, it's my Corsair flash drive. I noticed a while back that when WMP was running, my flash drive's access light would run non-stop until I closed WMP. This, as you can imagine, irked me to no end (for one, that light is really bright). I've gone into the Device options and changed the properties for my Corsair so all Sync options were unchecked. I've gone into the Advanced Options and disabled most of the "background sync" options. Yet still, from time to time (seemingly at random), my USB device will start flashing constantly when WMP11 is running, and won't stop until I close the program. After an exhaustive search on Google, I turned up no useful information. The only closely related posts I could find mentioned turning on manual syncing, or syncing when connected. Frankly, I don't want it to sync at all. I tried deleting the "DeviceInfo from the "WMPInfo.xml" file that WMP generates on my flash drive and seting the file to read-only, but that just causes WMP to crash whenever I open it and my flash drive is plugged in. So, I turn to you, in the hopes that someone reading this will have an answer on how to disable the sync feature for a particular device in WMP11. Barring that, I wouldn't mind turning off the sync feature altogether.

Anyone see the response, .

Say what you will, but Megabytes is universally accepted to mean 1024 Kilobytes, which equals 1024 Bytes. Which means there's 1,048,576 Bytes in a Megabyte. You can keep you Mebibytes, and shove it.

Ok, but what about the WIN51 files? I know WIN51IP2 goes on disc 2, but apparently that's not the only file as it's still not being recognized as disc 2. I combined the two discs together some time ago for service work so we'd be able to install on a customer's machine from the multiboot DVD, but now I can't remember the structure to split it. Obviously the CMPNENTS folder, but what else? *EDIT* Just realized I hadn't put the WIN51 file on the disc 2, but is there anything else I'm forgetting while I try this?

Sorry to ressurect an ancient thread, but I thought it would be interesting to find out what happened to this miracle "AV-killer". Anyone know if this guy turned out to be blowing smoke up our USB ports? Or was he actually on the level, and the software is out there now?

@hchant Your issue is a different one. You can't even connect to the printer. I can connect, but can't access it through RDP. @all I still haven't been able to find a solution to this. Is there no one who has come across this problem that has any ideas? Sorry to resurrect an old thread, but this is still ongoing and I need to find a solution. Currently, I have to use another computer to actually print anything through Terminal Services.

Doesn't look like that was the problem after all. I went back and looked for PCL6 drivers for Vista, and found them. But even after loading them up, it still doesn't work. Any suggestions?

You can't. You must do a fresh install of the x64 edition, upgrading is not possible. You can upgrade from one x86 version to another, or from one x64 version to another, but not from x86 to x64.

The printer is an HP LaserJet 1300 networked through a JetDirect. All our computers here at work are connected to our server through a VPN firewall. None of our computers are actually "on the domain", but they are on the same network as the domain server through the VPN. *EDIT* After checking the XP computers, I discovered that we have to run the PCL6 drivers in order for the printer to work through RDP. However, the only option I have for Vista and this printer is the PCL5 drivers. I wonder if this isn't the problem.

Ok, so I'm trying to remote desktop into a Windows Server 2003 domain server using Vista Ultimate x64. I had some initial problems setting up the login for the correct domain, but that's been rectified. However, I still have a problem that I can't seem to resolve. I've got our network printer setup on my computer and it works fine from Windows. But if I connect through RDP to the server, the printer isn't carried over, even though I checked the option to bring local printers to the remote desktop. I know in XP and 2000 I had to edit HKCU\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and add a FilterQueueType key to make the remote session see my printer. I tried to create that same key under Vista, but it didn't fix the problem. Any suggestions?

I find a simpler tool for boot image extraction is the command-line BBIE (Bart's Boot Image Extractor). Much simpler and smaller tool. If you know how, you can even add it to the context menu on drives, so you just right-click and extract the boot sector.

Ah, I didnt see this post before now. I would have made that "howto" earlier, but since WB5 is released now, and mostly everyone has it, I wont bother doing that.. Unless someone begs me to Its quite simple actually. Resize the wallpaper to the screen resolution, cut the bottom of the wallpaper so that it will fit the taskbar. Use Paintshop and create a 2 layer image, by using the taskbar bitmap and add a new layer that's around 70% opacue, paste the wallpaper cut and merge these two layers. Use a program called ResEdit to edit the msstyle, and change the taskbar bitmap to the one you made in paintshop. I realize this is an old post, but for others in the future I thought I'd post a simpler solution. At least if you own an Nvidia card. The NView option in the Nvidia drivers have supported changing the opacity of the Taskbar for some time now. From the classic Nvidia controls (might be possible from the new control panel, but I can't find it), go to Desktop Management and enable NView. Then scroll down to Effects and "Enable taskbar transparency" and set the desired level of opacity. Bingo. Though I have found when I play videos that the transparency turns off. And sometimes if a program is "using" the previously played video file, I have to close and reopen that file (whether it be a web browser, or some other program), before the transparency returns to normal.

So, anyone found a 64-bit resource editor yet? I've been looking around and I still haven't found one. Resource Tuner was supposed to have support for that by now, but still doesn't. I e-mailed them about it and am waiting to hear back. I'll keep looking, but hopefully someone's come across one by now.

Resource Hacker doesn't work for x64. It can't handle 64-bit executable files.

Hmm, after looking again, there is an option to "Search the Internet" on the search page. Though one would normally assume it wouldn't try connecting unless you click the link. Perhaps it's simply checking for internet connectivity, though that would be strange. Oh, well. Just something unusual I noticed and thought I'd post about.