SCOUG-HELP Mailing List Archives
Return to [ 11 |
October |
2005 ]
<< Previous Message <<
>> Next Message >>
1
This is a multi-part message in MIME format.
Content Type: text/plain
Content-Transfer-Encoding: 7bit
Sandy Shapiro wrote:
>In <434C0557.40906@linkline.com>, on 10/11/05
> at 11:32 AM, Wayne said:
>
>
>
>
>>Sandy, are you creating the partitions under OS/2 or under WinXP? I had
>>some similar problems some time back and I can't recall them in detail,
>>but my problem revolved around partition codes. If you're creating the
>>partitions under WinXP, an extended partition may be given a partition
>>code of "F" rather than "5"; OS/2 requires a "5" whereas WinXP will
>>accept either a "F" or a "5". HPFS and NTFS both use partition code "7".
>>
>>
>
>
>
>>You can use DFSEE to look at the partition codes and to change them;
>>experimenting shouldn't be a problem since you aren't yet using the
>>drive.
>>
>>
>
>Hi Wayne,
>
>I don't know how to create a fat32 partition using dfsee, and partition
>magic does not recognize my USB drive when I boot from a floppy. So I am
>using Partition Magic under WinXP to create the fat32 partition(s).
>
>DFSEE tells me that I have a logical 0b type of partition -- the same as
>the fat32 partition on my IDE hard drive. I have no trouble reading from,
>or writing to, the fat32 partition on the IDE drive. But on the USB drive,
>I get the error message "not formatted correctly."
>
>I tried taking a look with LVM and it says: Partition Table May be
>Corrupt. I suppose I could try going back to 32GB partitions, but that
>doesn't seem worth it.
>
>Sandy
>
>
>
Arrrgh, you're right, somehow I digressed from thinking about FAT32 to
thinking about NTFS & HPFS. "0b" is correct for FAT32.
But, my concern over the extended partition code still holds; you'll
probably have to use PTEDIT program from Partition Magic to look at the
extended partition code (Partition Magic may have created an extended
partition on the drive by default?). DFSEE doesn't seem to look at
extended partitions. I don't have a USB hard drive, so I'm not sure how
you run PTEDIT against it, since PTEDIT is DOS-based (maybe ask
PowerQuest how to manipulate the extended partition code on a USB
drive?). Perhaps you could use DFSEE to copy a similar setup (extended
and FAT32 partitions) from an IDE drive and then clone the IDE drive to
the USB drive and enlarge the FAT32 partition size using DFSEE???
....Sorry, I'm in over my head, as I don't use DFSEE very often, so I'm
just thinking random thoughts as I type.... I just think that an
extended partition code "F" could be the problem.
Wayne
Content Type: text/html
Content-Transfer-Encoding: 7bit
Sandy Shapiro wrote:
In <434C0557.40906@linkline.com>, on 10/11/05
at 11:32 AM, Wayne <waynec@linkline.com> said:
Sandy, are you creating the partitions under OS/2 or under WinXP? I had
some similar problems some time back and I can't recall them in detail,
but my problem revolved around partition codes. If you're creating the
partitions under WinXP, an extended partition may be given a partition
code of "F" rather than "5"; OS/2 requires a "5" whereas WinXP will
accept either a "F" or a "5". HPFS and NTFS both use partition code "7".
You can use DFSEE to look at the partition codes and to change them;
experimenting shouldn't be a problem since you aren't yet using the
drive.
Hi Wayne,
I don't know how to create a fat32 partition using dfsee, and partition
magic does not recognize my USB drive when I boot from a floppy. So I am
using Partition Magic under WinXP to create the fat32 partition(s).
DFSEE tells me that I have a logical 0b type of partition -- the same as
the fat32 partition on my IDE hard drive. I have no trouble reading from,
or writing to, the fat32 partition on the IDE drive. But on the USB drive,
I get the error message "not formatted correctly."
I tried taking a look with LVM and it says: Partition Table May be
Corrupt. I suppose I could try going back to 32GB partitions, but that
doesn't seem worth it.
Sandy
Arrrgh, you're right, somehow I digressed from thinking about FAT32 to
thinking about NTFS & HPFS. "0b" is correct for FAT32.
But, my concern over the extended partition code still holds; you'll
probably have to use PTEDIT program from Partition Magic to look at the
extended partition code (Partition Magic may have created an extended
partition on the drive by default?). DFSEE doesn't seem to look at
extended partitions. I don't have a USB hard drive, so I'm not sure how
you run PTEDIT against it, since PTEDIT is DOS-based (maybe ask
PowerQuest how to manipulate the extended partition code on a USB
drive?). Perhaps you could use DFSEE to copy a similar setup (extended
and FAT32 partitions) from an IDE drive and then clone the IDE drive to
the USB drive and enlarge the FAT32 partition size using DFSEE???
....Sorry, I'm in over my head, as I don't use DFSEE very often, so I'm
just thinking random thoughts as I type.... I just think that an
extended partition code "F" could be the problem.
Wayne
<< Previous Message <<
>> Next Message >>
Return to [ 11 |
October |
2005 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
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.
|