XP problem after installing Windows 8 in triple boot mode

I have a Toshiba laptop on which I installed at first both XP-SP2 (SP3 gave me problems) and Windows 7. Everything worked perfectly fine. W7 is on Physical Disk1 and XP on Physical Disk2.

Recently, I installed Windows 8 in triple boot mode on Disk1. Everything was fine with W7 and W8 but the W8 installation somewhat crippled XP:

When I booted into XP in triple boot mode, it would start off perfectly and then get into a loop before reaching the Desktop screen (same thing in Safe Mode). So, through W7, I reinstated the Base Registry in XP. Now, XP goes all the way to a normal operational mode except for the WiFi link. I can communicate with the modem; it asks for the Connect Password, but once entered, nothing happens: there is actually no connection to the Web. Whenever I ask for the status of the connection, I get the request for the password + confirmation.

Would anybody have a suggestion?

 

What devices are not showing up in Windows XP Device manager? Also, if you are just going to use Windows 7 as the main OS, I would install XP & 8 in a Virtual Machine, then get into triple booting, since you have to follow a certain procedure when installing Newer to older Operating systems.

See http://answers.microsoft.com/en-us/...o/af48d434-b725-4aa4-8aa9-e4a9cc30890f?auth=1 http://www.eightforums.com/installation-setup/10173-triple-booting-windows-8-win7-xp.html

 

Try turning off DHCP in the router and using the same static IP in each of the three systems. That ought to work.

 

Thank you for your replies.

The only device not showing (actually, the classical black exclamation mark on a yellow background) in both XP and W7 is an ACPI Controller. But that does not prevent W7 from working perfectly (and XP also, before the W8 installation).

Since I'm using 4 workstations, there are always static IP's. Here, it's 192.168.1.35.

My main OS is XP because it works beautifully and I have loads of programs on it. W7 is also OK now.

I was interested in solving this because it could be useful in other situations of this type. Anyhow, I had a clone of XP before the W8 installation which I could have used. I could also have used scannow. EasyBCD was also at hand if need be (the one compatible with W8) in case something went wrong with the MBR.

In the meantime, I found the solution. As usual, it's a "stupid" error. For some odd reason, TKIP replaced the original AES protocol. By restoring AES, the problem disappeared.

I really recommend people to have dual boot systems. Restoring the XP Base Registry through W7 was much simpler than all the operations you have to go through for this when you only have one system. All my pc's are dual boot xp/W7.

 

If you use WPA2 for wireless, wireless will use AES, not TKIP. You need to make sure that the router or Access Point is setup for "WPA-PSK (TKIP) and WPA2-PSK (AES)". Good to hear that it was just a simple error.

 

I'm intrigued by this comment. There is software available for backing up and restoring the Windows registry files but for the life of me I can't figure how Win 7 can help with this for XP. Care to go into a little more detail?

 

Under Windows 7, I clobbered the 5 files which make up the XP Base Registry. They're all in the REPAIR Directory. Clean as a whistle.

It's not W7 per se which is involved. It's any other OS you have available in a multiboot situation. It could have been any other Windows you have available. The idea is to access the faulty OS to repair it. From another active Windows, the faulty Windows is available as any passive series of passive directories.

 

"...the faulty Windows is available with its series of passive directories you can modify.

 

You can do that from virtually any bootable utilities disk, such as a Linux bootable CD. You don't need a Windows dual boot.

 

But the point is I succeeded with what I had. I didn't install dual boot to fix another OS. I did it because I preferred working under XP and wanted to see what Windows 7 looked like after the disastrous Vista "recommended by all laptop suppliers" as they are now recommending a disastrous Windows 8 which is only used by a little over 5% users worldwide after a release one year ago. But that's another story.

 

Come on - you are recommending ppl have a dual boot for this purpose. OK, it's one way of doing it, but there are far simpler ways.

 

Computer OEM's did not push for Vista, Microsoft did. They also killed it, the same as they are doing to Windows 8.

Now of course as of today, it was announced that Microsoft is buying the Nokia Handset division, due to they are losing face, and the company has to do anything to stay afloat at this point.

Microsoft has taken what is has described as a “bold” move of purchasing Nokia’s handset business in a deal worth €5.44bn (£4.6bn) that puts the company head to head with Apple and Google in the mobile hardware and software market.
http://www.marketingweek.co.uk/news/microsoft-buys-nokias-handset-business-for-46bn/4007794.article

Microsoft Corp. MSFT -4.55% made a case Tuesday for its $7 billion deal to acquire Nokia Corp.'s NOK1V.HE +33.94% struggling cellphone unit, a blockbuster transaction that solidifies the software giant's position as a distant No. 3 in the smartphone market.

As part of the deal for Nokia's devices-and-services business, Microsoft will bring aboard 32,000 Nokia employees including CEO Stephen Elop, who is believed to be among the contenders for Mr. Ballmer's job.
http://online.wsj.com/article/SB100...2112731349626.html?mod=WSJ_hps_LEFTTopStories

Now back to the task at hand. Earthling, I see no problem with using 7 to repair the XP registry, due to that is what the Pro versions of the OS were designed to do, was backwards compatibility, into the older version of Windows, through Remote Registry, and RDU.

I still hate it, when people will bash Vista, without getting the story straight. Dos 4.x was a disaster/failure, along with Windows Media Player 7.x. WinME was a failure due to lack of marketing, and hardware designers would not get on board. Vista again due to hardware designers would not get on board.

 

Do you really believe I installed a dual boot system on my machines several years ago only to fix a problem like this in case one day it popped up?

 

I beg to differ with brownizs on bashing Vista. As a user, I don't care what the story is behind Vista. I look at results and my "comfort" when working with an OS. It's a tremendous flop because it came out too soon without being sufficiently tested. Windows 8 will also be a flop (confirmed by GARTNER a year ago) because it doesn't answer users' needs but Microsoft's wishes. Practically all companies and knowledgeable users will stick with XP as long as they can and switch to Windows 7 when they decide to move up, if they haven't already done so.

 

Of course not. All of my computers have at least dual boot, some have triple boot. But if I want to make any changes to files that are normally inaccessible I use a boot disk rather than resorting to using a different version of Windows. That way I can avoid all of the permissions issues that can attend that approach.

You were advising ppl to have a dual boot for this purpose. It simply is not necessary or even advisable.