Replies

Why would anyone try to send anyone an Executable file when it’s way easier for them to send the link to the website they got it from???

Then, you can download the file yourself, if you choose to. This is the safest, simplest, and smartest way to share applications.

So, delete the mystery app, and ask your friend for the link. And then, all will be well.

“HP has a utility called PC Health which I used to upgrade anything that “needed updating” and I think that’s where my problem started.” PC Health worked like a charm under Vista.

But, Windows 7 does not need it, as all W7 Device Drivers are delivered via Windows updates (a new feature). There should never be any “W7-ONLY” Device Drivers listed on any manufacturer’s website. And, it’s for this reason that PC Health is no longer required, there are no W7 Drivers, and it was only written for VISTA.

TIP: If, for some reason, any are missing for your PC, you’d likely have to go to HP’s website and Manually download the latest VISTA drivers. It’s the manufacturer’s responsibility to provide Microsoft with all of their W7 drivers, ahead of time, including all computer manufacturers, and peripheral makers of Printers, Monitors, etc. And, x64 drivers, in particular, are still a problem.

I also have an Acer 3000 Series laptop, and Linux Mint 7 recognized my BroadCom 4.3 Internal WiFi without a hitch.

But, when I removed Mint 7, and installed Mint 8, I had the same problem as you did. So, I used Mint 8’s built-in NdisWrapper and found the XP driver on my XP partition for BroadCom and Mint 8 is now “humming”. Now, if I could only remember the exact method I used!

TIP: Try Mint 7 FIRST, it is the easiest way.

I have been using CrossLoop since the very beginning, too, and it’s an excellent tool!

It beats Windows built-in Remote Assistance by a “country mile”, in ease of use, and security & reliability, and it’s free! http://www.crossloop.com

TIP: Using Skype, PC to PC, in conjunction with CrossLoop, can slow the remote PC down to a crawl, and yours too, unless the PCs have lots of RAM (1 – 3 GB, depending on Windows version).

Is it possible to install win7 over windows xp. What am i going to lose?

MaryG’s suggestion to use the Windows 7 Upgrade Advisor, free from Microsoft, is “bang on”. W7UA will tell you if going to W7 is even an option. That said:

There is no XP to “W7 Upgrade” Option, so you must do a W7 “Custom Install”, which formats the XP partition, and wipes out all your personal data (so, Back Up XP, first!), unless you choose to set up a dual-boot configuration. An XP back up is the only way to ensure that you won’t lose anything. The full procedure, including how to do the back up, is printed (on paper) in the W7 Upgrade kit.

Side Bar:

The solution to Mike Rule’s BIOS Boot issue is a little GEM called EasyBCD (free). It puts XP into the W7 Boot Loader screen. Google for it…

FYI: You can still use a W7 Upgrade kit for use with XP, there is no need to BUY a full version of W7. In fact, there’s an article on http://www.windowssecrets.com that explains how to do a Vista to W7 Upgrade, and then, convert that to a full Custom Install without losing all your Vista stuff, legally!

Re: JoeP’s comment about voiding previous Activation Codes, that can happen when Upgrading to W7, but the “jury’s still out” when using the Custom Install, despite what Microsoft implies. http://www.windowssecrets.com discusses the confusion over this issue, too. This is not an attempt at ‘flaming”, but for clarification.

“One has Vista 64 on it with other files, 300gb drive. One I use for data, 500gb drive and the other is now empty, formatted NTFS, 75gb.”

With that much storage, you have lots of choices! If you have all your personal data from Vista on your Data drive, my best advice is: Do NOT do the Upgrade to Windows 7.

Microsoft’s Upgrades never worked perfectly in the past, and I wouldn’t trust them to work flawlessly NOW. 98 to XP still sticks in my craw, and I didn’t even try for XP to Vista.

Here’s what I did:

I installed W7 Ultimate, as a dual-boot configuration, on my second hard drive (essentially, my SandBox), but did not Activate it (< This Is Critical!) Then, I took the time to get comfortable with W7, and tested all Vista apps and verified my Vista data was usable, within the 30 activation period. Then, and only then, I started again, and did the W7 "Custom Install", and formatted my Vista partition. In both cases, W7's Windows Updates found all the required device drivers, and everything worked perfectly. I'm "SandBoxing" Linux Mint 8, next.

“After closing the VM, Win 7 keyboard shortcuts are disabled.”

Before you can safely shut down VMware, or any other Virtual Machine, you must shut down all running Operating Systems, FIRST.

Just like you would if your Windows weren’t running inside a VM. Shutting down a VM, while OSes are still running, is exactly the same as pulling the AC plug out of the wall on a REAL computer!