SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sat, 27 Sep 2003 13:05:19 PDT7
From:	waynec@linkline.com
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: 40gb IDE drive - fixed!

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Gary Wong writes:

> Wayne:
>
> I have a few questions:
> 1) Did you install an XP service pack? I seem to recall that with Win2000 > you had to install at least SP 1 or else it would clobber Boot Manager.

The WinXP install from the WinXP cdrom does clobber Boot Manager... which
was the beginning of my problem, I couldn't get it set up again because
FDISK wouldn't allow me to create a boot manager partition on the ide drive.

Yes, I did install the current service (everything that Microsoft
recommended after inspecting my WinXP partition at their service webpage),
after I installed WinXP from the WinXP cdrom.

> 2) Which version of Partition Magic did you use?

Version 5, for the most part (I did a lot of looking and poking at the hard
drives over the last few days), but also used version 7 for the ptedit
program it contains.

Wayne

**************************************************************************
>
> On Sat, 27 Sep 2003 01:01:40 PDT7, waynec@linkline.com wrote:

>>I got bootmanager working! Now I can choose to boot Windows XP Pro or Warp.
>>Tried a LOT of things before I worked through the problems. It was
>>apparently a combination of things.
>>
>>Hate to say it, but it looks like it was primarily the same issue I had last
>>spring: partition type codes. I'm not positive, because I did several
>>changes that made it work (and tried many more before that).
>>
>>First I deleted the boot manager partition from my first scsi drive, then
>>physically disconnected the two scsi drives, and then was able to use FDISK
>>(from Warp install diskettes, plus a utility diskette) to create a boot
>>manager partition on the still-connected ide drive... that's something I
>>wasn't able to do with the scsi drives connected (FDISK refused to put a
>>boot manager partition on the ide drive, it had that option greyed-out).
>>
>>So I could then boot WinXP from the bootmanager screen.
>>
>>But when I reconnected the scsi drives, the Warp partition showed up on the
>>bootmanager screen, but I still couldn't boot Warp from the bootmanager
>>screen... I kept getting that "OS/2 is not able to operate your hard disk or
>>diskette drive" message.
>>
>>So I took another hard look at the ide drive with the ptedit utility, and
>>this time I located a code "F" on one partition, and I changed it to a "5".
>>I hadn't seen this code in prior inspections, so I'm not sure if I
>>overlooked it or if it wasn't there. "F" is the code later Windows versions
>>use for an extended partition, whereas Warp only recognizes a "5" for that
>>usage.
>>
>>That did the trick, now on the bootmanager screen WinXP C: shows up on the
>>first (ide) drive, the Warp partition is D: on the second (first scsi)
>>drive, and both will boot!
>>
>>FYI, the WinXP partition is formatted as NTFS, which has the same partition
>>code ("7") as HPFS. WinXP sees the HPFS partitions, it just can't access
>>them, so when they are cursor-clicked in Explorer, WinXP presents a message
>>asking if you want to format the partition. Likewise, Warp can't access the
>>NTFS partition.
>>
>>Wayne
>>
>>************** copy of my initial post follows ***************************
>>
>>waynec@linkline.com writes:
>>
>>> You may recall my travails last June as I tried to install a 40gb IDE
>>> drive on a new barebones computer which also has (2) 9gb scsi drives.
>>> I am once again having difficulties, and I am hoping someone here can
>>> steer me in the right direction.
>>>
>>> Due to an illness (and subsequent death) in the family, I was away for
>>> several months and not using the new system. Before I left I had it
>>> working quite well, with a WinXP system on the ide and a Warp system on
>>> the scsi, set up for boot manager, and could boot and run either.
>>>
>>> Very soon after returning home, I caught the "w32.swen" virus on WinXP
>>> (see my reply post on the "returned email" thread), and I ended up
>>> trashing that partition before it was over.
>>>
>>> I have rebuilt the WinXP partition, and had to let the install program
>>> reformat the partition and remove it from the boot manager, as it will
>>> only install WinXP to the first primary partition on the first drive. Now
>>> I can't get boot manager working correctly and I can't remember exactly
>>> how I had previously set it all up, or how I had the WinXP partition
>>> formatted.
>>>
>>> The ide drive has:
>>> - a 4gb primary NTFS partition with WinXP (label "WinXP"),
>>> - a freespace of 1 cylinder in case I want a boot manager here
>>> - a hidden HPFS logical Warp partition that is not currently in use,
>>> - a lot of freespace.
>>>
>>> The first scsi drive has:
>>> - an OS/2 bootmanager partition,
>>> - a hidden FAT16 partition ("C_subst") for use as a substitute C:
>>> partition in case I need to disconnect the ide drive,
>>> - a hidden Warp HPFS logical partition ("Warp1vol") for emergency
>>> maintenance use,
>>> - a Warp HPFS ("ScsiWarp") logical partition
>>> - 3 FAT16 data logical partitions
>>> - 3 FAT16 one-cylinder placekeeper logical partitions (simply there to
>>> allow drive letters that follow to match another computer)
>>> - an HPFS logical data partition
>>>
>>> The second scsi drive has a single HPFS logical data partition that is
>>> currently empty.
>>>
>>> FDISK, run from updated install diskettes, shows all 3 hard drives, mapped
>>> correctly. PQmagic ver5, strangely, sees the ide and the first scsi drive,
>>> mapped correctly, but doesn't show the second scsi drive.
>>>
>>> The Bios is set up to boot from the first scsi drive to bring up OS/2
>>> bootmanager. If I put Warp1vol and ScsiWarp (only) in bootmanager, the
>>> boot manager screen shows these partitions (with Warp1vol as hidden) as C:
>>> drives, which is incorrect, because I need them to be D: drives.
>>> Apparently it doesn't recognize the ide drive primary partition.
>>>
>>> I have tried to put WinXP in the bootmanager, but strangely, the partition
>>> that shows up in the bootmanager screen is the bootmanager itself, an 8mb
>>> partition (I have done multiple iterations, and this IS what it does).
>>>
>>> If I highlight that 8mb partition entry and hit enter, it simply
>>> highlights the ScsiWarp entry.
>>>
>>> If I try to boot ScsiWarp from the boot manager screen, I get the initial
>>> bootup selection/timer screens, followed immediately by the message "OS/2
>>> is not able to operate your hard disk or diskette drive." Hard wait.
>>>
>>> If I "unhide" the C_subst partition, the boot manager screen shows the 2
>>> scsi partitions as D: drives, but if I boot ScsiWarp, I get the same "OS/2
>>> is not able...." message.
>>>
>>> If I disconnect the ide drive and "unhide" C_subst, then OS/2 boots fine.
>>>
>>> If I reconnect the ide drive,and change the bios to boot from the ide
>>> drive, then WinXP boots up fine.
>>>
>>> I tried moving the boot manager partition to the ide drive. Same problems.
>>>
>>> I have run chkdsk against the scsi partition and it is fine. I have tried
>>> to run diagnostics against the WinXP drive, but WinXP won't do that while
>>> it is running, rather it asks you if you want to schedule a run for the
>>> next bootup, and if you do so, it seems to take a long time booting but no
>>> messages are shown (blank screen) before the normal signon screen, so it's
>>> difficult to tell what happened. I have to assume that the drives are OK,
>>> since I can boot one or the other of the two operating systems, I just
>>> can't get them both on the boot manager screen, nor can I boot ScsiWarp
>>> when the ide drive is connected.
>>>
>>> One questionable area: I think (I'm not certain) I may have formatted the
>>> WinXP partition as FAT32 originally back in June; this time it was
>>> formatted as NTFS. HPFS and NTFS both have partition code "07". Could this
>>> be a problem? I am reticent to go through yet another WinXP install and
>>> customization just to find out. Other partition codes on the drives appear
>>> to be normal OS/2 codes.
>>>
>>> What else should I look at to resolve this problem so I can use boot
>>> manager?
>>>
>>> Wayne
>>>
>>>
>>> =====================================================
>>>
>>> To unsubscribe from this list, send an email message
>>> to "steward@scoug.com". In the body of the message,
>>> put the command "unsubscribe scoug-help".
>>>
>>> For problems, contact the list owner at
>>> "rollin@scoug.com".
>>>
>>> =====================================================
>>>
>>>
>>
>>
>>=====================================================
>>
>>To unsubscribe from this list, send an email message
>>to "steward@scoug.com". In the body of the message,
>>put the command "unsubscribe scoug-help".
>>
>>For problems, contact the list owner at
>>"rollin@scoug.com".
>>
>>=====================================================
>>
>>
>>
>
>
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================
>
>

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 27 | September | 2003 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.