Windows 98 & ME - Problem with accessing a partition

Page 1 of 2

Show 40 post(s) from this thread on one page

Win98banter (http://www.win98banter.com/index.php)

- Disk Drives (http://www.win98banter.com/forumdisplay.php?f=6)

- - Problem with accessing a partition (http://www.win98banter.com/showthread.php?t=48163)

Andrew[_2_]

May 18th 10 12:26 PM

Problem with accessing a partition

My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I have on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D: (logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:. Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP partition,
by resizing it (while in a hidden status). I did it with the aid of Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK and I
could easily access the files on the D: and E: partitions. However, I was
unable to access files on D: from Win98se - their names were scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size, clicking on D:
issued a message of the type: “D:\ is not accessible, a system device doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Hot-text

May 18th 10 05:54 PM

Problem with accessing a partition

No C:\ @500MB for MSDOS need for AutoExec.bat, Boot, Config.sys, bootsect,
boot.ini, NTDETECT.COM, msdownld.tmp
VIDEOROM.BIN, + More
For the way you have it XP Boot is in win 98 For all the BOOT are in WIN98
you need C:\ for DOS LOOL!

D:\win98
E:\XP
F:\ so on, so on

"Andrew" wrote in message
...
My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I have
on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D: (logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of
Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:. Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP
partition,
by resizing it (while in a hidden status). I did it with the aid of
Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK and I
could easily access the files on the D: and E: partitions. However, I was
unable to access files on D: from Win98se - their names were scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size, clicking on
D:
issued a message of the type: “D:\ is not accessible, a system device
doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Hot-text

May 18th 10 05:54 PM

Problem with accessing a partition

Hot-text

May 18th 10 07:26 PM

Problem with accessing a partition

P.S. the XP needed the 80 GB to run good!
O by the way the only Drive you can make Bigger is the last Dive
If you make C:\ bigger it will take the Free Space from D:\
If you make D:\ bigger it will take the Free Space from E:\
If you make E:\ bigger it will take the Free Space from F:\
If you make F:\ bigger it will take the Free Space from G:\
If you make G:\ bigger it will take the Free Space from unallocated,
primary, 87.5 GB

you have to move the Space down form to unallocated
You can not give D:/ 3gb if all the Free Space from E:\ have is to you have
to Move Free Space Down!
OK

So Start over

"Hot-text" wrote in message
...
No C:\ @500MB for MSDOS need for AutoExec.bat, Boot, Config.sys,
bootsect, boot.ini, NTDETECT.COM, msdownld.tmp
VIDEOROM.BIN, + More
For the way you have it XP Boot is in win 98 For all the BOOT are in
WIN98
you need C:\ for DOS LOOL!

D:\win98
E:\XP
F:\ so on, so on

"Andrew" wrote in message
...
My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I have
on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D: (logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of
Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:. Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP
partition,
by resizing it (while in a hidden status). I did it with the aid of
Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK and I
could easily access the files on the D: and E: partitions. However, I was
unable to access files on D: from Win98se - their names were scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size, clicking on
D:
issued a message of the type: “D:\ is not accessible, a system device
doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Hot-text

May 18th 10 07:26 PM

Problem with accessing a partition

Hot-text

May 18th 10 07:45 PM

Problem with accessing a partition

P.S.S

Move Free Space Down from unallocated!
First you need to Defragmentation All Drives
then Restart Computer
Move unallocated Space Down one Drive
Then Defragmentation That Drive
then Restart Computer
Move from that Drive some Free Space Down one Drive
Then Defragmentation The two Drives
then Restart Computer
Move from that Drive some Free Space Down one Drive
Then Defragmentation The three Drives
then Restart Computer
Move from that Drive some Free Space Down one Drive
Then Defragmentation The fore Drives
then Restart Computer

So on So On!!!

For that's the way to do it

Have Fun

"Hot-text" wrote in message
...
P.S. the XP needed the 80 GB to run good!
O by the way the only Drive you can make Bigger is the last Dive
If you make C:\ bigger it will take the Free Space from D:\
If you make D:\ bigger it will take the Free Space from E:\
If you make E:\ bigger it will take the Free Space from F:\
If you make F:\ bigger it will take the Free Space from G:\
If you make G:\ bigger it will take the Free Space from unallocated,
primary, 87.5 GB

you have to move the Space down form to unallocated
You can not give D:/ 3gb if all the Free Space from E:\ have is to you
have to Move Free Space Down!
OK

So Start over

"Hot-text" wrote in message
...
No C:\ @500MB for MSDOS need for AutoExec.bat, Boot, Config.sys,
bootsect, boot.ini, NTDETECT.COM, msdownld.tmp
VIDEOROM.BIN, + More
For the way you have it XP Boot is in win 98 For all the BOOT are in
WIN98
you need C:\ for DOS LOOL!

D:\win98
E:\XP
F:\ so on, so on

"Andrew" wrote in message
...
My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I
have on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D: (logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of
Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:. Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP
partition,
by resizing it (while in a hidden status). I did it with the aid of
Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK and I
could easily access the files on the D: and E: partitions. However, I
was
unable to access files on D: from Win98se - their names were scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size, clicking
on D:
issued a message of the type: “D:\ is not accessible, a system device
doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my
system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Hot-text

May 18th 10 07:45 PM

Problem with accessing a partition

Andrew[_2_]

May 18th 10 10:50 PM

Problem with accessing a partition

Thanks for fast reaction and your suggestions I'm afraid they don't answer my
questions.
1. Are you really familiar with Partition Magic 8?
It does everyting nicely fand automatically for you, although it has to go
through several steps you are suggesting. It does this using its Wizard(s)
and you decide to some extent how to do it. I've been using it for quite a
time without any problems at all, even in the described by me configuration.
2. In order to make a partition bigger you have to have free space in the
adjacent partition, not necessarily the next one, as you are suggesting.
3. I don't need C: for DOS either
4. If you use D: for Win 98, then you can't have WinXP in E:, as this is
equivalent of having 2 active partitions at any time, which would only ask
for a disaster. I agree, however, that WinXP should be installed in the
partition following directly Win98, which is the case on my hard disk.

"Hot-text" wrote:

P.S. the XP needed the 80 GB to run good!
O by the way the only Drive you can make Bigger is the last Dive
If you make C:\ bigger it will take the Free Space from D:\
If you make D:\ bigger it will take the Free Space from E:\
If you make E:\ bigger it will take the Free Space from F:\
If you make F:\ bigger it will take the Free Space from G:\
If you make G:\ bigger it will take the Free Space from unallocated,
primary, 87.5 GB

you have to move the Space down form to unallocated
You can not give D:/ 3gb if all the Free Space from E:\ have is to you have
to Move Free Space Down!
OK

So Start over

"Hot-text" wrote in message
...
No C:\ @500MB for MSDOS need for AutoExec.bat, Boot, Config.sys,
bootsect, boot.ini, NTDETECT.COM, msdownld.tmp
VIDEOROM.BIN, + More
For the way you have it XP Boot is in win 98 For all the BOOT are in
WIN98
you need C:\ for DOS LOOL!

D:\win98
E:\XP
F:\ so on, so on

"Andrew" wrote in message
...
My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I have
on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D: (logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of
Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:. Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP
partition,
by resizing it (while in a hidden status). I did it with the aid of
Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK and I
could easily access the files on the D: and E: partitions. However, I was
unable to access files on D: from Win98se - their names were scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size, clicking on
D:
issued a message of the type: “D:\ is not accessible, a system device
doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Andrew[_2_]

May 18th 10 10:50 PM

Problem with accessing a partition

Hot-text

May 19th 10 07:59 AM

Problem with accessing a partition

I really familiar with Partitioning all Software work the some when in
making a Partition!
You have to move the Free Space down from drive to drive Magic 8 can help
in the moving of the Free Space and
Have to Defragment as you go too!

our you will have Fragment it one Drive that go to the Fragment of the Drive
you made bigger!
and the drive will stop working!
Remember that why you here right!

"Andrew" wrote in message
...
Thanks for fast reaction and your suggestions I'm afraid they don't answer
my
questions.
1. Are you really familiar with Partition Magic 8?
It does everyting nicely fand automatically for you, although it has to go
through several steps you are suggesting. It does this using its Wizard(s)
and you decide to some extent how to do it. I've been using it for quite a
time without any problems at all, even in the described by me
configuration.
2. In order to make a partition bigger you have to have free space in the
adjacent partition, not necessarily the next one, as you are suggesting.
3. I don't need C: for DOS either
4. If you use D: for Win 98, then you can't have WinXP in E:, as this is
equivalent of having 2 active partitions at any time, which would only ask
for a disaster. I agree, however, that WinXP should be installed in the
partition following directly Win98, which is the case on my hard disk.

"Hot-text" wrote:

P.S. the XP needed the 80 GB to run good!
O by the way the only Drive you can make Bigger is the last Dive
If you make C:\ bigger it will take the Free Space from D:\
If you make D:\ bigger it will take the Free Space from E:\
If you make E:\ bigger it will take the Free Space from F:\
If you make F:\ bigger it will take the Free Space from G:\
If you make G:\ bigger it will take the Free Space from unallocated,
primary, 87.5 GB

you have to move the Space down form to unallocated
You can not give D:/ 3gb if all the Free Space from E:\ have is to you
have
to Move Free Space Down!
OK

So Start over

"Hot-text" wrote in message
...
No C:\ @500MB for MSDOS need for AutoExec.bat, Boot, Config.sys,
bootsect, boot.ini, NTDETECT.COM, msdownld.tmp
VIDEOROM.BIN, + More
For the way you have it XP Boot is in win 98 For all the BOOT are in
WIN98
you need C:\ for DOS LOOL!

D:\win98
E:\XP
F:\ so on, so on

"Andrew" wrote in message
...
My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I
have
on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D:
(logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of
Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:. Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP
partition,
by resizing it (while in a hidden status). I did it with the aid of
Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK and
I
could easily access the files on the D: and E: partitions. However, I
was
unable to access files on D: from Win98se - their names were
scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size, clicking
on
D:
issued a message of the type: “D:\ is not accessible, a system device
doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my
system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Hot-text

May 19th 10 07:59 AM

Problem with accessing a partition

Andrew[_2_]

May 19th 10 03:50 PM

Problem with accessing a partition

Hot-text, I appreciate your efforts, I really do and I don't want to say that
your ideas are flat wrong.
The point is that you don't read my text carefully enough and consequently
you are not addressing my problems.
Most likely, this is also why you didn't notice that the drive I made bigger
worked perfectly OK before and after the resizing, which is in contradiction
to what you are claiming in this post.

"Hot-text" wrote:

I really familiar with Partitioning all Software work the some when in
making a Partition!
You have to move the Free Space down from drive to drive Magic 8 can help
in the moving of the Free Space and
Have to Defragment as you go too!

our you will have Fragment it one Drive that go to the Fragment of the Drive
you made bigger!
and the drive will stop working!
Remember that why you here right!

"Andrew" wrote in message
...
Thanks for fast reaction and your suggestions I'm afraid they don't answer
my
questions.
1. Are you really familiar with Partition Magic 8?
It does everyting nicely fand automatically for you, although it has to go
through several steps you are suggesting. It does this using its Wizard(s)
and you decide to some extent how to do it. I've been using it for quite a
time without any problems at all, even in the described by me
configuration.
2. In order to make a partition bigger you have to have free space in the
adjacent partition, not necessarily the next one, as you are suggesting.
3. I don't need C: for DOS either
4. If you use D: for Win 98, then you can't have WinXP in E:, as this is
equivalent of having 2 active partitions at any time, which would only ask
for a disaster. I agree, however, that WinXP should be installed in the
partition following directly Win98, which is the case on my hard disk.

"Hot-text" wrote:

P.S. the XP needed the 80 GB to run good!
O by the way the only Drive you can make Bigger is the last Dive
If you make C:\ bigger it will take the Free Space from D:\
If you make D:\ bigger it will take the Free Space from E:\
If you make E:\ bigger it will take the Free Space from F:\
If you make F:\ bigger it will take the Free Space from G:\
If you make G:\ bigger it will take the Free Space from unallocated,
primary, 87.5 GB

you have to move the Space down form to unallocated
You can not give D:/ 3gb if all the Free Space from E:\ have is to you
have
to Move Free Space Down!
OK

So Start over

"Hot-text" wrote in message
...
No C:\ @500MB for MSDOS need for AutoExec.bat, Boot, Config.sys,
bootsect, boot.ini, NTDETECT.COM, msdownld.tmp
VIDEOROM.BIN, + More
For the way you have it XP Boot is in win 98 For all the BOOT are in
WIN98
you need C:\ for DOS LOOL!

D:\win98
E:\XP
F:\ so on, so on

"Andrew" wrote in message
...
My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I
have
on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D:
(logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of
Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:. Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP
partition,
by resizing it (while in a hidden status). I did it with the aid of
Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK and
I
could easily access the files on the D: and E: partitions. However, I
was
unable to access files on D: from Win98se - their names were
scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size, clicking
on
D:
issued a message of the type: “D:\ is not accessible, a system device
doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my
system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Andrew[_2_]

May 19th 10 03:50 PM

Problem with accessing a partition

Hot-text

May 20th 10 08:41 AM

Problem with accessing a partition

Look the the drive You made bigger Will worked perfectly OK True, But the
Dive after it will stop working
Because you are moving Space form that Drive and making it smaller, Not from
the end of the Disk where the unallocated is for it will always be the same
Sizes! until you make the last drive partition bigger, or make a new
partition Drive! That why you move the bigger Down for.

You Defragment Because the Info on the Disk looks like this

01010101010 Free Space 01010101010 Free Space Free Space 01010101010 Free
Space 01010101010 Free Space Free Space
You to Defragment the move the info like this
01010101010010101010100101010101001010101010 Free Space Free Space Free
Space Free Space Free Space Free Space

That way you move the Free Space down not the info 01010

if you move the Info, that Drive it will stop working afterwards but the
bigger one Will worked perfectly
and if you Save a file in the bigger perfectly working afterwards you may
not be able to work that drive no more!

So that is the problems being address here right!

If project requires technicians to do service then call one.

They do for $35 to $45 a hour you look at a 3 to 6 hour job!

"Andrew" wrote in message
...
Hot-text, I appreciate your efforts, I really do and I don't want to say
that
your ideas are flat wrong.
The point is that you don't read my text carefully enough and consequently
you are not addressing my problems.
Most likely, this is also why you didn't notice that the drive I made
bigger
worked perfectly OK before and after the resizing, which is in
contradiction
to what you are claiming in this post.

"Hot-text" wrote:

I really familiar with Partitioning all Software work the some when in
making a Partition!
You have to move the Free Space down from drive to drive Magic 8 can
help
in the moving of the Free Space and
Have to Defragment as you go too!

our you will have Fragment it one Drive that go to the Fragment of the
Drive
you made bigger!
and the drive will stop working!
Remember that why you here right!

"Andrew" wrote in message
...
Thanks for fast reaction and your suggestions I'm afraid they don't
answer
my
questions.
1. Are you really familiar with Partition Magic 8?
It does everyting nicely fand automatically for you, although it has to
go
through several steps you are suggesting. It does this using its
Wizard(s)
and you decide to some extent how to do it. I've been using it for
quite a
time without any problems at all, even in the described by me
configuration.
2. In order to make a partition bigger you have to have free space in
the
adjacent partition, not necessarily the next one, as you are
suggesting.
3. I don't need C: for DOS either
4. If you use D: for Win 98, then you can't have WinXP in E:, as this
is
equivalent of having 2 active partitions at any time, which would only
ask
for a disaster. I agree, however, that WinXP should be installed in the
partition following directly Win98, which is the case on my hard disk.

"Hot-text" wrote:

P.S. the XP needed the 80 GB to run good!
O by the way the only Drive you can make Bigger is the last Dive
If you make C:\ bigger it will take the Free Space from D:\
If you make D:\ bigger it will take the Free Space from E:\
If you make E:\ bigger it will take the Free Space from F:\
If you make F:\ bigger it will take the Free Space from G:\
If you make G:\ bigger it will take the Free Space from unallocated,
primary, 87.5 GB

you have to move the Space down form to unallocated
You can not give D:/ 3gb if all the Free Space from E:\ have is to you
have
to Move Free Space Down!
OK

So Start over

"Hot-text" wrote in message
...
No C:\ @500MB for MSDOS need for AutoExec.bat, Boot, Config.sys,
bootsect, boot.ini, NTDETECT.COM, msdownld.tmp
VIDEOROM.BIN, + More
For the way you have it XP Boot is in win 98 For all the BOOT are
in
WIN98
you need C:\ for DOS LOOL!

D:\win98
E:\XP
F:\ so on, so on

"Andrew" wrote in message
...
My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD
I
have
on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D:
(logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5
GB).
All partitions are FAT32, created with the aid of Partition Magic
(of
Power
Quest).
Both OSs have been installed independently of each other.
I keep documents and photos on D: and some older backups on E:.
Both
partitions are easily accesible for the active OS.
Yesterday, I tried to cross the 32GB limit (by 3GB) on the WinXP
partition,
by resizing it (while in a hidden status). I did it with the aid of
Partition
Magic 8.0 in Win 98se. After this resizing WinXP seemed to work OK
and
I
could easily access the files on the D: and E: partitions. However,
I
was
unable to access files on D: from Win98se - their names were
scrumbled.
Strangely enough files on E: were accesible.
After resizing the WinXP partition down to the previous size,
clicking
on
D:
issued a message of the type: “D:\ is not accessible, a system
device
doesn’t
work”. However, restarting Win98se returned everything to normal.
Do you have any idea about the reason of such a behavior?
Is there any chance to use bigger than 32 GB WinXP partition on my
system
without compromising normal work of Win98se?
Thanks for your help,
Andrew

Hot-text

May 20th 10 08:41 AM

Problem with accessing a partition

Steven Saunderson

May 21st 10 11:53 AM

Problem with accessing a partition

On Tue, 18 May 2010 04:26:01 -0700, Andrew
wrote:

My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I have on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D: (logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of Power
Quest).

Can you provide any more details about the partitions ?
a) Why doesn't the WinXP partition have a drive letter ? If they're all
FAT32 then Win98 should see them all.
b) Are the partitions FAT32 LBA (type 0x0C) or FAT32 CHS (type 0x0B) ?
c) Is the extended partition type 0x05 or 0x0F ?

I don't have any definite ideas about the problem but some more details
might help. Although the drive is 160GB you've only allocated about
73GB so it should all be accessible via 28-bit LBA.

Cheers,
--
Steven

Steven Saunderson

May 21st 10 11:53 AM

Problem with accessing a partition

Andrew[_2_]

May 22nd 10 12:19 PM

Problem with accessing a partition

More details!
a. I run the WinXP Home edition.
If you assign the active partition, Partition Magic hides automatically the
other primary partitions, as having 2 active would call for disaster.
Therefore lack of the letter. If I want to start WinXP, then I make its
partition active and Win98 is automatically starred. My both OSs use the
letter C:, as working partition must be on the primary disk (disk 0) on the
partition C:. On the hard disk my WinXP partition is located directly after
the Win98 one.
b&c. My MoBo and hard disk support LBA48. My partitions, according to
Partition info a
Win98se 0C (Hex) FAT32X
WinXP 1C FAT32X
Extended 0F Extended X
D: 0C FAT32
E: 0B FAT32
Unallocated.
(The WinXP, D:, and E: partitions use also FAT extensions - VFAT LFNS)
I must add that after resizing the WinXP partition (from Win98) to 35GB, I
could make accesibility checks on D: without restarting computer to Win98.
Yet, the E: partition was accessible under these conditions.
Regards,
Andrew

"Steven Saunderson" wrote:

On Tue, 18 May 2010 04:26:01 -0700, Andrew
wrote:

My 160GB Western Digital (48-bit LBA), PATA hard disk (the only HD I have on
this machine) is for a reason partitioned as follows:
C: (Win98se, primary, 14.5GB), * (WinXP, primary, 30.6GB), D: (logical,
11.8GB), E: (logical, 7.6 GB) and * (unallocated, primary, 87.5 GB).
All partitions are FAT32, created with the aid of Partition Magic (of Power
Quest).

Can you provide any more details about the partitions ?
a) Why doesn't the WinXP partition have a drive letter ? If they're all
FAT32 then Win98 should see them all.
b) Are the partitions FAT32 LBA (type 0x0C) or FAT32 CHS (type 0x0B) ?
c) Is the extended partition type 0x05 or 0x0F ?

I don't have any definite ideas about the problem but some more details
might help. Although the drive is 160GB you've only allocated about
73GB so it should all be accessible via 28-bit LBA.

Cheers,
--
Steven
.

Andrew[_2_]

May 22nd 10 12:19 PM

Problem with accessing a partition

Steven Saunderson

May 22nd 10 12:55 PM

Problem with accessing a partition

On Sat, 22 May 2010 04:19:01 -0700, Andrew
wrote:

More details!
a. I run the WinXP Home edition.
If you assign the active partition, Partition Magic hides automatically the
other primary partitions, as having 2 active would call for disaster.
Therefore lack of the letter. If I want to start WinXP, then I make its
partition active and Win98 is automatically starred.

This makes sense but it isn't really necessary. I used to setup disks
with two primary partitions (and an extended one) and install a backup
version of the OS on the second primary one. If the user got into big
problems I would change the bootable flag from the first to the second
and start the PC using the backup OS. Then I could fix the real OS in
the first partition and then restore the bootable flags so the PC ran
normally. It sounds like Partition Magic changes the type of the
partition (e.g. 0C to FF) to make it inaccessible. This shouldn't cause
a problem unless you want to access the disabled partition (e.g. to back
it up).

Partition info a
Win98se 0C (Hex) FAT32X
WinXP 1C FAT32X
Extended 0F Extended X
D: 0C FAT32
E: 0B FAT32

It looks like D: is FAT32X (type 0x0C) which is good. I don't like the
fact that E: is type 0x0B. Win98 IO.SYS has a problem when encountering
a mix of LBA and CHS volumes in the extended partition.

Can you change the type of D: from 0x0B to 0x0C ? I think this will fix
the problem. If you can't then please check
http://home.exetel.com.au/~phelum/w98.htm to read about my fix for
Win98 IO.SYS.

Cheers,
--
Steven

Steven Saunderson

May 22nd 10 12:55 PM

Problem with accessing a partition

Steven Saunderson

May 22nd 10 01:08 PM

Problem with accessing a partition

On Sat, 22 May 2010 21:55:48 +1000, Steven Saunderson
wrote:

Can you change the type of D: from 0x0B to 0x0C ?

Oops, that should be change the type of E: from 0x0B to 0x0C.

Cheers,
--
Steven

Steven Saunderson

May 22nd 10 01:08 PM

Problem with accessing a partition

On Sat, 22 May 2010 21:55:48 +1000, Steven Saunderson
wrote:

Can you change the type of D: from 0x0B to 0x0C ?

Oops, that should be change the type of E: from 0x0B to 0x0C.

Cheers,
--
Steven

Andrew[_2_]

May 22nd 10 05:44 PM

Problem with accessing a partition

Thanks for your comments and hints.
I'm afraid that it's impossible to make such a conversion in Partition Magic.
I have to apologize for informing you incorrectly about the D: partition.
In fact, both the D: and E: partitions are 0B (Hex).

Regards,
Andrew

"Steven Saunderson" wrote:

On Sat, 22 May 2010 04:19:01 -0700, Andrew
wrote:

More details!
a. I run the WinXP Home edition.
If you assign the active partition, Partition Magic hides automatically the
other primary partitions, as having 2 active would call for disaster.
Therefore lack of the letter. If I want to start WinXP, then I make its
partition active and Win98 is automatically starred.

This makes sense but it isn't really necessary. I used to setup disks
with two primary partitions (and an extended one) and install a backup
version of the OS on the second primary one. If the user got into big
problems I would change the bootable flag from the first to the second
and start the PC using the backup OS. Then I could fix the real OS in
the first partition and then restore the bootable flags so the PC ran
normally. It sounds like Partition Magic changes the type of the
partition (e.g. 0C to FF) to make it inaccessible. This shouldn't cause
a problem unless you want to access the disabled partition (e.g. to back
it up).

Partition info a
Win98se 0C (Hex) FAT32X
WinXP 1C FAT32X
Extended 0F Extended X
D: 0C FAT32
E: 0B FAT32

It looks like D: is FAT32X (type 0x0C) which is good. I don't like the
fact that E: is type 0x0B. Win98 IO.SYS has a problem when encountering
a mix of LBA and CHS volumes in the extended partition.

Can you change the type of D: from 0x0B to 0x0C ? I think this will fix
the problem. If you can't then please check
http://home.exetel.com.au/~phelum/w98.htm to read about my fix for
Win98 IO.SYS.

Cheers,
--
Steven
.

Andrew[_2_]

May 22nd 10 05:44 PM

Problem with accessing a partition

Steven Saunderson

May 22nd 10 07:45 PM

Problem with accessing a partition

On Sat, 22 May 2010 09:44:07 -0700, Andrew
wrote:

Thanks for your comments and hints.
I'm afraid that it's impossible to make such a conversion in Partition Magic.
I have to apologize for informing you incorrectly about the D: partition.
In fact, both the D: and E: partitions are 0B (Hex).

This sounds like a manifestation of the IO.SYS bug I mentioned. You
have CHS partitions in an LBA type extended partition. This is not
necessarily invalid (although a bit silly) but in your case I'd say it
is actually wrong because they all exceed the 8.4GB barrier.

You could try either a modified IO.SYS or use a disk editor program to
change the partition types from 0x0B to 0x0C.

Cheers,
--
Steven

Steven Saunderson

May 22nd 10 07:45 PM

Problem with accessing a partition

Andrew[_2_]

May 27th 10 09:11 PM

Problem with accessing a partition

While browsing the Partition Magic installation CD-ROM, I found extra
utilities on it. One of them was the ptedit32.exe, i.e., Partition Table
Editor v1.1 of 2002. The nice thing about this editor is that it is still
downloadable from the Internet and its interface is in plain English.

I used it to change my 0Bs to 0Cs, but I failed. To be more precise, I was
able to make such changes with this utility and save them (they even were in
place after rebooting the computer), but everything returned to the previous
situation, as soon, as I opened Partition Magic.

Although your reasoning about my logical partitions seems to be OK, there is
probably another limitation or maybe a deficiency of Partition Magic, which
doesn't allow it. By the way, I found on the Internet an another example of
the similar situation with 2 logical 0B partitions within the ExtenedX
partition (cf. www.goodells.net.multiboot.ptedit.htm).

I'm sure that I didn't make any mistake, so simple this interface was.
Its starting screen displays the master boot sector and master partition
table with its 4 entries and their types (in my case: 1C, 0C, 0F and 00 for
the Win98, WinXP, Extended and Unallocated partitions, respectively).
Clicking on 'Boot Record', displays all the boot record details of the
particular partitions.
Consecutive use of the 'Goto EPBR' option moves to the Extended partition
table with my chained logical volumes as the first entries.
Finally, the 'Set Type' option allows to change the partition type.
I would be grateful for your comments, if the above description is useful
somehow.

Regards,
Andrew

"Steven Saunderson" wrote:

On Sat, 22 May 2010 09:44:07 -0700, Andrew
wrote:

Thanks for your comments and hints.
I'm afraid that it's impossible to make such a conversion in Partition Magic.
I have to apologize for informing you incorrectly about the D: partition.
In fact, both the D: and E: partitions are 0B (Hex).

This sounds like a manifestation of the IO.SYS bug I mentioned. You
have CHS partitions in an LBA type extended partition. This is not
necessarily invalid (although a bit silly) but in your case I'd say it
is actually wrong because they all exceed the 8.4GB barrier.

You could try either a modified IO.SYS or use a disk editor program to
change the partition types from 0x0B to 0x0C.

Cheers,
--
Steven
.

Andrew[_2_]

May 27th 10 09:11 PM

Problem with accessing a partition

Steven Saunderson

May 28th 10 06:30 AM

Problem with accessing a partition

On Thu, 27 May 2010 13:11:31 -0700, Andrew
wrote:

While browsing the Partition Magic installation CD-ROM, I found extra
utilities on it. One of them was the ptedit32.exe, i.e., Partition Table
Editor v1.1 of 2002. The nice thing about this editor is that it is still
downloadable from the Internet and its interface is in plain English.

I used it to change my 0Bs to 0Cs, but I failed. To be more precise, I was
able to make such changes with this utility and save them (they even were in
place after rebooting the computer), but everything returned to the previous
situation, as soon, as I opened Partition Magic.

A simple test here might show whether we're on the right track. Use
Partition Magic to make your Win98 system partition active and then use
ptedit.exe (I assume you boot using a DOS floppy to use ptedit) to
change the partition types from 0B to 0C. Then you could start Win98
and see if it can see the partitions properly and also that you have no
phantom drives in Explorer. Phantom drives have a drive letter but if
you try to view them in Explorer it will tell you the volume isn't
formatted. If the partitions don't appear then the problem is
elsewhere.

Although your reasoning about my logical partitions seems to be OK, there is
probably another limitation or maybe a deficiency of Partition Magic, which
doesn't allow it. By the way, I found on the Internet an another example of
the similar situation with 2 logical 0B partitions within the ExtenedX
partition (cf. www.goodells.net.multiboot.ptedit.htm).

The partition type code issue is a bit muddled due to historical
factors. Type 0x0B is FAT32 with CHS access and type 0x0C is FAT32 with
LBA access. I believe that Win98 respects this. But all versions of
Win NT always use LBA access. So XP doesn't care whether your
partitions are 0x0B or 0x0C; it always uses LBA. If I create a FAT32
volume in XP it always gets the 0x0B code even when it's past the 1024
cylinder boundary. So if Partition Magic does the same I wouldn't call
it a bug or even a deficiency. But it can cause problems with Win98
IO.SYS so it seems a bit silly to me.

So please try the ptedit test above and tell me if it helps. I think a
better long-term solution would be to make your system multiboot with
the Win98 system partition as the active partition. Then you could
select which O/S you want at boot time and not have to play with
changing the partition table. I think this can be done without mucking
up the drive letters in either O/S. Does this approach appeal to you ?

Cheers,
--
Steven

Steven Saunderson

May 28th 10 06:30 AM

Problem with accessing a partition

Andrew[_2_]

May 28th 10 11:29 PM

Problem with accessing a partition

1. I always use Partition Magic for DOS (on rescue disks) to make the Win98se
partition active. This version doesn't have all options of the Windows
version. In order to complete the changes made to my hard drive(s), I have to
reboot to Win98se.
2. No, I never used ptedit.exe, which is the DOS version of this editor, but
ptedit32.exe, running it either from Win98 or from WinXP. Under such
circumstances, I never had phantom drives in Explorer.
3. Is use of the ptedit.exe (from DOS) essential for the suggested by you
test?
4. MS approach to multibooting has documented disadvantages, especially in
case you decide to get rid of Win98 at a later time. A better solution would
be multibooting approach of Partition Magic. My approach separating
completely both OSs isn't perfect either, but fortunately, I'm not switching
too often to Win98 and believe to abandon it anyway within a year or so.

Regards,
Andrew

"Steven Saunderson" wrote:

On Thu, 27 May 2010 13:11:31 -0700, Andrew
wrote:

While browsing the Partition Magic installation CD-ROM, I found extra
utilities on it. One of them was the ptedit32.exe, i.e., Partition Table
Editor v1.1 of 2002. The nice thing about this editor is that it is still
downloadable from the Internet and its interface is in plain English.

I used it to change my 0Bs to 0Cs, but I failed. To be more precise, I was
able to make such changes with this utility and save them (they even were in
place after rebooting the computer), but everything returned to the previous
situation, as soon, as I opened Partition Magic.

A simple test here might show whether we're on the right track. Use
Partition Magic to make your Win98 system partition active and then use
ptedit.exe (I assume you boot using a DOS floppy to use ptedit) to
change the partition types from 0B to 0C. Then you could start Win98
and see if it can see the partitions properly and also that you have no
phantom drives in Explorer. Phantom drives have a drive letter but if
you try to view them in Explorer it will tell you the volume isn't
formatted. If the partitions don't appear then the problem is
elsewhere.

Although your reasoning about my logical partitions seems to be OK, there is
probably another limitation or maybe a deficiency of Partition Magic, which
doesn't allow it. By the way, I found on the Internet an another example of
the similar situation with 2 logical 0B partitions within the ExtenedX
partition (cf. www.goodells.net.multiboot.ptedit.htm).

The partition type code issue is a bit muddled due to historical
factors. Type 0x0B is FAT32 with CHS access and type 0x0C is FAT32 with
LBA access. I believe that Win98 respects this. But all versions of
Win NT always use LBA access. So XP doesn't care whether your
partitions are 0x0B or 0x0C; it always uses LBA. If I create a FAT32
volume in XP it always gets the 0x0B code even when it's past the 1024
cylinder boundary. So if Partition Magic does the same I wouldn't call
it a bug or even a deficiency. But it can cause problems with Win98
IO.SYS so it seems a bit silly to me.

So please try the ptedit test above and tell me if it helps. I think a
better long-term solution would be to make your system multiboot with
the Win98 system partition as the active partition. Then you could
select which O/S you want at boot time and not have to play with
changing the partition table. I think this can be done without mucking
up the drive letters in either O/S. Does this approach appeal to you ?

Cheers,
--
Steven
.

Andrew[_2_]

May 28th 10 11:29 PM

Problem with accessing a partition

Steven Saunderson

May 29th 10 12:24 AM

Problem with accessing a partition

On Fri, 28 May 2010 15:29:01 -0700, Andrew
wrote:

3. Is use of the ptedit.exe (from DOS) essential for the suggested by you
test?

No, you could use any suitable program. But it might be safer to do the
changes outside of Win98 (e.g. DOS) because you are seeing the problem
when running Win98. Also you mentioned the difference after a reboot
which suggests that some of the effects of the change are only detected
when Win98 is starting.

4. MS approach to multibooting has documented disadvantages, especially in
case you decide to get rid of Win98 at a later time.

Yup, nothing's perfect. For instance NTLDR has a limitation of 10
entries in the BOOT.INI file. Of course, only silly people like me will
ever hit this limit so it's not really a problem.

Cheers,
--
Steven

Steven Saunderson

May 29th 10 12:24 AM

Problem with accessing a partition

Andrew[_2_]

May 29th 10 09:23 PM

Problem with accessing a partition

1. To be precise, I was able to make the 0B-0C changes with (pedit32.exe)
and save them (either in Win98 or WinXP). They were in place after rebooting
the computer. However, these changes disappeared, after opening of Partition
Magic (either in DOS or in Windows). It seems, Partition Magic didn't accept
the changes, for some reason.

2. Just to be on a safe side, I performed the suggested by you test. This
time, I restarted the computer from Win98 to DOS and then ran pedit.exe from
a floppy). The results were the same as before.

3. To check, if my E: partitions (of only 7.5GB) wasn't a culprit, I used
Partition Magic from DOS (rescue disks) to enlarge it by 1 GB and then
repeated the test, but the results were the same, as before.

4. Some data listed in the Boot Record Table for the partition E: in
ptedit.exe seem to me strange, namely
- Hidden Sectors: 117852903
- First Cluster of Root: 141346
These are rather big numbers, whereas for D: they a 63 and 2, respectively.

5. Finally, in my Extended Partition Table, there are 2 non-zero entries in
the Type column: 0B describing my D: partition (I corrected it to 0C) and 05,
which describes an Extended Partition and not the ExtendedX one, which should
have 0F entry, as in the Partition Table at sector 0. I don't understand this
either and I didn't correct it.

Regards,
Andrew

"Steven Saunderson" wrote:

On Fri, 28 May 2010 15:29:01 -0700, Andrew
wrote:

3. Is use of the ptedit.exe (from DOS) essential for the suggested by you
test?

No, you could use any suitable program. But it might be safer to do the
changes outside of Win98 (e.g. DOS) because you are seeing the problem
when running Win98. Also you mentioned the difference after a reboot
which suggests that some of the effects of the change are only detected
when Win98 is starting.

4. MS approach to multibooting has documented disadvantages, especially in
case you decide to get rid of Win98 at a later time.

Yup, nothing's perfect. For instance NTLDR has a limitation of 10
entries in the BOOT.INI file. Of course, only silly people like me will
ever hit this limit so it's not really a problem.

Cheers,
--
Steven
.

Andrew[_2_]

May 29th 10 09:23 PM

Problem with accessing a partition

Steven Saunderson

May 30th 10 11:46 AM

Problem with accessing a partition

On Sat, 29 May 2010 13:23:01 -0700, Andrew
wrote:

2. Just to be on a safe side, I performed the suggested by you test. This
time, I restarted the computer from Win98 to DOS and then ran pedit.exe from
a floppy). The results were the same as before.

Thanks for trying.

4. Some data listed in the Boot Record Table for the partition E: in
ptedit.exe seem to me strange, namely
- Hidden Sectors: 117852903
- First Cluster of Root: 141346
These are rather big numbers, whereas for D: they a 63 and 2, respectively.

These are strange values. The hidden sectors value suggests that the
data is nowhere near the boot record. This could indicate how Partition
Magic moves data when you resize a partition.

5. Finally, in my Extended Partition Table, there are 2 non-zero entries in
the Type column: 0B describing my D: partition (I corrected it to 0C) and 05,
which describes an Extended Partition and not the ExtendedX one, which should
have 0F entry, as in the Partition Table at sector 0. I don't understand this
either and I didn't correct it.

The 0x05 is correct. The continuation entries are always 0x05 even when
the extended partition starts with a 0x0F code.

I'm rather lost here because I don't know anything about Partition
Magic. Assume that originally your disk had two primary partitions and
then your extended one with two volumes. When you increased the size of
the second primary partition perhaps PM made space by moving the D:
volume to after the E: volume and changing the links in the extended
partition to suit. It would be easier to move 11GB than 30GB. As far
as I know each partition has to be contiguous but the volumes in the
extended partition can have spare areas between them and don't have to
be in ascending order by disk address.

It's a double-edged sword. PM is very clever in that it can resize
partitions but it might be producing layouts that confuse things like
Win98. It should be possible to determine your disk layout by using
something like Ranish Partition Manager but changing things to help
Win98 might cause problems when you later use PM to resize a partition
or select the other O/S.

Hopefully someone with ideas or knowledge of PM will chip in here. I'm
hesitant to suggest further changes due to the risk of wrecking your
setup.

It is possible to have Win98 and XP on a disk and select the one you
want by changing the boot flag using something like FDISK. This used to
be common in the old days and I still do it on some PCs.

Cheers,
--
Steven

Steven Saunderson

May 30th 10 11:46 AM

Problem with accessing a partition

Andrew[_2_]

May 31st 10 12:23 AM

Problem with accessing a partition

Thanks a lot for your interesting comments and helpful ideas.
I'm sorry to bother you again with my questions, hopefully last time, but
this might lead to a breakthrough.

1. These are strange values. The hidden sector values suggest that the data is nowhere near the boot record. This could indicate how Partition Magic moves data when you resize a partition.

My logical partitions D: and E: are not system partitions. They are so to
say chained within my Extended partition. Can these strange values mean that
the boot record for E: is located just before the beginning of E: and that
these values reflect their relative distance from the beginning of the
Extended partition? Is such a description used for logical partitions?

2. As far as I know each partition has to be contiguous but the volumes in the extended partition can have spare areas between them and don't have to be in ascending order by disk address.

This is a very important info that I was unaware of. Let me return here to
the PM resizing procedure.
To resize my WinXP(*:) partition located in the following sequence of
partitions: [C: Win98, (*:) WinXP, D:, E:, Unallocated] by 7GB, PM had to go
through 5 'elementary' steps in the order displayed below:
a. Resize Extended (*:) by 7GB (taken from Unallocated)
b. Move E: up by 7GB
c. Move D: up by 7GB
d. Resize Extended (*:) down by 7GB
e. Resize WinXP (*:) by 7GB
Are these details somehow useful for confirmation of your idea about these
strange values?

3. It is possible to have Win98 and XP on a disk and select the one you want by changing the boot flag using something like FDISK.

You're completely right. One can easily do it, e.g. in the ptedit32.exe, by
changing the flags. 'Boot flags' 00 and 80 stand for not bootable and
bootable, and 'type flags' 0C and 1C stand for FAT32X and Hidden Fat32X
partitions, respectively. PM has also 2 additional utilities (BootDisk) for
activation and/or deactivation of a primary partition. One can easily change
them.

Regards,
Andrew

"Steven Saunderson" wrote:

On Sat, 29 May 2010 13:23:01 -0700, Andrew
wrote:

2. Just to be on a safe side, I performed the suggested by you test. This
time, I restarted the computer from Win98 to DOS and then ran pedit.exe from
a floppy). The results were the same as before.

Thanks for trying.

4. Some data listed in the Boot Record Table for the partition E: in
ptedit.exe seem to me strange, namely
- Hidden Sectors: 117852903
- First Cluster of Root: 141346
These are rather big numbers, whereas for D: they a 63 and 2, respectively.

These are strange values. The hidden sectors value suggests that the
data is nowhere near the boot record. This could indicate how Partition
Magic moves data when you resize a partition.

5. Finally, in my Extended Partition Table, there are 2 non-zero entries in
the Type column: 0B describing my D: partition (I corrected it to 0C) and 05,
which describes an Extended Partition and not the ExtendedX one, which should
have 0F entry, as in the Partition Table at sector 0. I don't understand this
either and I didn't correct it.

The 0x05 is correct. The continuation entries are always 0x05 even when
the extended partition starts with a 0x0F code.

I'm rather lost here because I don't know anything about Partition
Magic. Assume that originally your disk had two primary partitions and
then your extended one with two volumes. When you increased the size of
the second primary partition perhaps PM made space by moving the D:
volume to after the E: volume and changing the links in the extended
partition to suit. It would be easier to move 11GB than 30GB. As far
as I know each partition has to be contiguous but the volumes in the
extended partition can have spare areas between them and don't have to
be in ascending order by disk address.

It's a double-edged sword. PM is very clever in that it can resize
partitions but it might be producing layouts that confuse things like
Win98. It should be possible to determine your disk layout by using
something like Ranish Partition Manager but changing things to help
Win98 might cause problems when you later use PM to resize a partition
or select the other O/S.

Hopefully someone with ideas or knowledge of PM will chip in here. I'm
hesitant to suggest further changes due to the risk of wrecking your
setup.

It is possible to have Win98 and XP on a disk and select the one you
want by changing the boot flag using something like FDISK. This used to
be common in the old days and I still do it on some PCs.

Cheers,
--
Steven
.

All times are GMT +1. The time now is 01:30 PM.

Page 1 of 2

Show 40 post(s) from this thread on one page