Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

New XP install does not recognize new partition on HDD

- - - - -

  • Please log in to reply
4 replies to this topic

#1
oldtiger64

oldtiger64
  • Member
  • 2 posts
  • Joined 24-February 15
  • OS:XP Pro x86
  • Country: Country Flag

Long story short, I have the need to install my legal copy of Windows XP on a new 64 bit AMD HP 455G1 laptop running Windows 7 Pro, because my old software does not operate correctly in the XP virtual machine mode!

 

So, I added a new 80GB partition (currently W) on the HDD of my laptop. I was able to get the XP SATA driver for another model HP AMD laptop, and have slipstreamed my Windows XP SP2, SP3 and x86 driver into an ISO file using nLite.

 

The installation works fine up to the point where it asks where to install XP and the partition (W) I created is not shown, so setup stops.

 

Any ideas how I can get my laptop to recognize the new partition? As you all know there ain't nobody out there supporting XP anymore, and that is a crying shame!

 

oldtiger64




How to remove advertisement from MSFN

#2
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,158 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
Do you mean that you can see "other" *partitions* but not the "W:" one?
Strictly speaking the "W:" is not a partition it is a drive letter assigned to a volume, or even more exactly it is a mounpoint for the volume implicitly created inside the partition you created.
Even if the XP setup can see that volume, it will assign to it by default a different letter (much "lower", like E: , provided that you have the hidden windows7 partition, a "normal" largish partition as C: and a DVD drive with letter D: )
But, depending on the size of the hard disk and on where (towards the beginning or the end of the disk) you created the partition you may be affected by the so-called LBA48 barrier, roughly around 128Gb.
In any case installing an XP on a disk where 7 has been already installed needs a couple tricks to later allow for dual booting.

Can you post some more details on your hardware and describe EXACTLY how you created the added 80 Gb partition?

jaclaz

#3
oldtiger64

oldtiger64
  • Member
  • 2 posts
  • Joined 24-February 15
  • OS:XP Pro x86
  • Country: Country Flag

jaclaz, thank you for your response, first off let me say my computer experience is limited so some of your terms and comments my be over my head!

 

The computer that I need XP is a HP ProBook 455G1, with an AMD A6-4400 M APU. *GB RAM runnining a 64 bit copy of Windows 7.

 

The 698GB HDD hard drive is partitioned as follows C: Windows 604.18GB, D: Recovery 11.45GB, E: Tools 1.99GB, :System (no drive letteror size showing) and the drive I installed W: 80.0GB using Windows 7 disk management tools to shrink the existing space on the main drive

 

Windows disk management shows all drives as healthy and I can write and read data to the W: drive I created without any problem. The W: drive is showing as 3 in the list of the 5, between C: and D: (Again, my terminology may not be correct, but hopefully this gives you a better understanding of my current dsetup)

 

I really appreciate you trying to help me!

 

oldtiger64

.



#4
bphlpt

bphlpt

    MSFN Addict

  • Member
  • PipPipPipPipPipPipPip
  • 1,908 posts
  • Joined 12-May 07
  • OS:none specified
  • Country: Country Flag

@oldtiger64, I think this is the main piece of info that is still missing.
 

...describe EXACTLY how you created the added 80 Gb partition?

 
Cheers and Regards


Edited by bphlpt, Yesterday, 12:21 PM.

Posted Image


#5
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,158 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Yep. :yes:, now it is much more clear.

If you reduced the "thing" that you see as C: from the original 604 Gb to roughly 524 Gb in order to create the 80 Gb "thing" that you see as W:, then the "W: thing" begins past the 128 Gb mark in any case, no matter if the "C: thing" is actually at the beginning of the disk or not (usually it comes after the "system" partition, which should be normally 100 Mb in size).

The issue is detailed here:
http://support.micro...kb/303013/en-us

It is possible - for any reason - that the EnableBigLBA setting is not in the Registry of the Setup CD you made  :unsure: nlite should have made that set properly, but you never know.

But there is also another problem.

The "system" partition (that MS insists on calling the other way round) is actually the "boot" partition, see:
http://www.multiboot....uk/system.html

Basically what you see as "system" and without a drive letter assigned is a primary partition with an ID of 0x27 (this is a "special" partition ID that makes Windows 7 NOT assign a drive letter to it), which is actually a NTFS formatted volume inside a partition that is marked as "Active" (and that would normally have a partition ID of 0x07).

Windows XP knows nothing about a partition with ID 0x27, and this is very likely to create issues when installing, once the other issue has been solved.

Bear with me, please.

Right now your PC boot sequence is the following:
BIOS->MBR->bootsector of the Active partition (the "no drive letter", "system" partition with ID 0x27)-> BOOTMGR ( residing also on the "no drive letter", "system" partition with ID 0x27)->choices in \boot\BCD( residing also on the "no drive letter", "system" partition with ID 0x27)-> WINLOAD.EXE (residing on the "C: thing")-> Windows 7

The normal booting sequence of XP is instead:
BIOS->MBR->bootsector of the Active partition (which cannot be of type 0x27, and it is usually at the same time "system" and "boot" volume, and that in your case will probably correspond to the "W: thing" )->NTLDR (residing on the "W: thing")->choices in BOOT.INI (also residing on the "W: thing")->Windows XP kernel (also residing on the "W: thing").

In other words, even once we will manage to have the XP install "see" the "W: thing" you should NOT proceed to install.
IF you do install in that situation AND the XP install gives no issues, you will lose the possibility of booting to the Windows 7 (and it might be tricky to fix the situation), while IF you do install in that situation BUT the XP install has any issue, you will have a completely NON bootable system, i.e. both XP and 7 will fail loading) :ph34r:

All MS OS installs are "predatory" in the sense that they take over the boot sequence, altering it along the lines of what they think is "best".
Of course when you install a later OS (let's say a Windows 7 after having installed the XP) the setup has an automatic option to "import" the existing previous OS booting, but obviously a previous OS knows nothing about a later one and simply writes the "own" boot sequence.

A procedure is given here (option 2):
http://www.sevenforu...ndows-7-xp.html
BUT it is NOT advised (by me) to follow that method, as it gives you not any control on drive letter assignment (in the XP) and it is more generally "risky" and needing tools that I (personally) do not recommend.

Still it is useful :) as a reference.
Right now you did what is detailed on that guide under "option 2" up to point 5, I believe.

Questions:

1) What do you see right now at that step?
(I need to understand what is the situation now, before suggesting you how to go on).
2) Can you (if needed) re-create the .iso (with or without nlite)?
3) Do you have a PE of some kind (please describe) or the Windows 7 install DVD?

 

jaclaz






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users