Jan N. Waliszewski
>Do you know if Partition Magic 6.0 still handles HPFS partitions ? The
>marketing leaflets don't mention HPFS as the filesystem which the new
>version can handle...
Yes, it does.
--
-John (John.T...@attglobal.net)
> In <3B67C57A...@t-system.com.pl>, Jan Waliszewski <jan.wal...@t-system.com.pl> writes:
>
> >Do you know if Partition Magic 6.0 still handles HPFS partitions ? The
> >marketing leaflets don't mention HPFS as the filesystem which the new
> >version can handle...
>
> Yes, it does.
What about LVM?
--
John Varela
Partition Magic erases the data that LVM places in the partition table
that is used to identify the assigned drive letter (among other
things).
After PM is used on partitions you have to run LVM (or VCU) again to
create "Volumes" from the partitions that were manipulated with PM. If
you resize your boot drive, your system will not boot (no drive letter
assignment for the boot partition) so you have to boot from CD or
diskette and run LVM to create the "C:" volume - assuming C is your
boot drive...
LVM is a partitioning and "volume management" tool. You can have HPFS,
JFS, and/or FAT file systems in LVM "volumes"
--
Lorne Sunley
Michael Iwaki
iw...@gte.net
> I bought Partition Magic 6.0 yesterday and installed in on my Windows NT4
> partition. In the manual, they say that HPFS as well as HPFS/386 (which
> is used by OS/2 Advanced Server) is handled.
This is new! Powerquest gave me really bad advice regarding HPFS386
when I inquired about using PM5.0 with HPFS386 about two years ago. I'd
sure like to hear from someone who's actually successfully resized an
HPFS386 partition using PM6 .
--
Regards,
Al S.
* Hillman & Rootes Group manuals online: http://asavage.fdns.net/Hillman
* Ford Falcon manuals online: http://FalconFAQ.fdns.net
This OS/2 system ("Tori", W4 FP15) uptime is 0 days 16:37 hours
> I bought Partition Magic 6.0 yesterday and installed in on my Windows NT4
> partition. In the manual, they say that HPFS as well as HPFS/386 (which
> is used by OS/2 Advanced Server) is handled. Also FAT, FAT32, Linux Ext2
> , Linux Swap, NTFS file systems are handled. Version 6.0 is meant to
> install on all recent Windows versions: Win 95/98/Me and Win NT4 (with
> SP4 or higher) and Win 2000. It also comes with the means of creating
> two rescue floppy disks... Disk1 is bootable and is essentially a PCDOS
> bootable floppy with disk utilities: DOS's FDISK, Ptedit, Partinfo
> (partition table information utility) , chkdsk and other stuff. Disk 2 is
> a program disk and has other stuff. These rescue disks can be installed
> on DOS, OS/2, linux or run off the floppy drive as barebones DOS. I am
> going to try it out by creating a Linux ext2 partition for data. Hope it
> works!
I have PM 5, and it works fine with ext2 partitions.
--
To reply to this message, replace everything to the left of "@" with
james.knott.
> I bought Partition Magic 6.0 yesterday and installed in on my Windows
> NT4 partition. In the manual, they say that HPFS as well as HPFS/386
> (which is used by OS/2 Advanced Server) is handled. Also FAT, FAT32,
> Linux Ext2 , Linux Swap, NTFS file systems are handled. Version 6.0 is
> meant to install on all recent Windows versions: Win 95/98/Me and Win
> NT4 (with SP4 or higher) and Win 2000. It also comes with the means of
> creating two rescue floppy disks... Disk1 is bootable and is essentially
> a PCDOS bootable floppy with disk utilities: DOS's FDISK, Ptedit,
> Partinfo (partition table information utility) , chkdsk and other stuff.
> Disk 2 is a program disk and has other stuff. These rescue disks can
> be installed on DOS, OS/2, linux or run off the floppy drive as
> barebones DOS. I am going to try it out by creating a Linux ext2
> partition for data. Hope it works!
It works well for Linux partitions and is invaluable when one need to
inevitably resize any type of partition (except LVM volumes of course).
Do I understand correctly, that a Linux ext2 partition *can* be resized? I need that...
Tnx
David
Mike Tuthill wrote:
has the stupid HPFS extended patition type bug been fixed then ?
>>It works well for Linux partitions and is invaluable when one need to
>>inevitably resize any type of partition (except LVM volumes of course).
>
> Do I understand correctly, that a Linux ext2 partition *can* be resized?
> I need that...
That's correct. I've used PM to resize, split and move ext2 partitions. I
used the bootable floppies to run PM.
>>It works well for Linux partitions and is invaluable when one need to
>>inevitably resize any type of partition (except LVM volumes of course).
>
> Do I understand correctly, that a Linux ext2 partition *can* be resized?
> I need that...
That is correct. I've done it on numerous occasions using PM with no
problems.
I really don't know. You might want to check the PowerQuest site for
that info.
> > has the stupid HPFS extended patition type bug been fixed then ?
>
> I really don't know. You might want to check the PowerQuest site for
> that info.
>
Is this actually referring to the MS 'lets break ranks and change what
type an extended partition is stored at' "feature" or is there a bug
with HPFS and extended partitions?
if its the latter can someone tell me what it is as I've had HPFS and
extended partitions for years without prob's maybe I've just been
lucky.
--
Richard A Crane ph 08 8945 3252 fx 08 8945 5952
Check Copyright of this with the author or you may suffer litigation
or embarrassment.
Richard Crane wrote:
>
> Is this actually referring to the MS 'lets break ranks and change what
> type an extended partition is stored at' "feature" or is there a bug
> with HPFS and extended partitions?
> if its the latter can someone tell me what it is as I've had HPFS and
> extended partitions for years without prob's maybe I've just been
> lucky.
>
MS actually made their extendX partitions type 0f and tied it to their
fix for having partitions larger than 2 GB or accessing partitions
beyond the 1024 cylinder limit to the existence of the 0f partition.
Thus, if some snob failed to use MS invention and had a partition larger
than 2 GB of went and used the space out beyond 1024, then the data
pointer in the file system would wrap and over write his data. MS then
could say it was the boob's fault for not installing MS fix. Now none
other operating systems acknowledge MS tricks. Why should other vendors
kowtow to MS moving target of tricks?
--
Bill
<Okay, you win>
Richard Crane wrote:
>On Wed, 15 Aug 2001 02:14:20, "Mike Tuthill" <miket...@home.com>
>wrote:
>
>>>has the stupid HPFS extended patition type bug been fixed then ?
>>>
>>
>>I really don't know. You might want to check the PowerQuest site for
>>that info.
>>
>Is this actually referring to the MS 'lets break ranks and change what
>type an extended partition is stored at' "feature" or is there a bug
>with HPFS and extended partitions?
>if its the latter can someone tell me what it is as I've had HPFS and
>extended partitions for years without prob's maybe I've just been
>lucky.
>
Yes it's the MS thing
But the change is so stupid because Only OS/2 can read HPFS ext. part.
over 4G.(pinball stops at 4) but if you use PM5 (I svear it's the last
version of PM that I'll buy) to resize *OR* copy an ext. pr. you are
left with a partition that no operating system can read and I would have
to classify that as a bug .
I mean if you copy a partition and the new copy is another partiton type
then it's not an exact copy plain and simple.
Of course DFSee fixes this easily, but users blame the OS since they do
not know whats happening
I've gone back to 3.03 DOS & OS2, funnily enough the DOS 3.03 version
works on my 30 Gig drive but the 3.05 version does not, that version
tells me to go buy V4 if I want to use drives larger than 8g !?
marketing ......
> Yes it's the MS thing
>
> But the change is so stupid because Only OS/2 can read HPFS ext. part.
> over 4G.(pinball stops at 4) but if you use PM5 (I svear it's the last
> version of PM that I'll buy) to resize *OR* copy an ext. pr. you are
> left with a partition that no operating system can read and I would have
> to classify that as a bug .
>
> I mean if you copy a partition and the new copy is another partiton type
> then it's not an exact copy plain and simple.
>
>
> Of course DFSee fixes this easily, but users blame the OS since they do
> not know whats happening
>
> I've gone back to 3.03 DOS & OS2, funnily enough the DOS 3.03 version
> works on my 30 Gig drive but the 3.05 version does not, that version
> tells me to go buy V4 if I want to use drives larger than 8g !?
>
> marketing ......
>
No lets this clear, MS changed their use of the identifier of extended
partitions. There is no 'bug' in OS/2 or HPFS involved at all.
Richard Crane wrote:
>
> On Fri, 17 Aug 2001 03:28:54, Olafur Gunnlaugsson <o...@oli.is> wrote:
>
> > Yes it's the MS thing
> >
> > But the change is so stupid because Only OS/2 can read HPFS ext. part.
> > over 4G.(pinball stops at 4) but if you use PM5 (I swear it's the last
> > version of PM that I'll buy) to resize *OR* copy an ext. pr. you are
> > left with a partition that no operating system can read and I would have
> > to classify that as a bug .
> >
> >
> No lets this clear, MS changed their use of the identifier of extended
> partitions. There is no 'bug' in OS/2 or HPFS involved at all.
>
I think he was speaking of a bug in PM writing of the partition table,
and not anything OS/2.
I was talking about PM's handling of HPFS partitions as buggy, what on
earth made you think I was referring to an OS/2 bug ?
My reading of your original post which said:
"has the stupid HPFS extended patition type bug been fixed then ?"
Ok in retrospect I can see that you were talking about PM but I didn't
originally. BTW I find the best work around is to either send MS to
the dump or limit it to small partitions in FAT.
Michael Iwaki
Olafur Gunnlaugsson wrote:
If you mean the type '0f' extended-x partition bug, it is still there. I
ran into it when I created a new partition above the 8GB mark on my disk
drive. The extended partition was type '05' , the standard extended
partition but after the operation, it was changed to type '0f'. I panicked a
little and asked some people about it. The solution is simple:
In the two rescue diskettes created, there is a program called ptedit.exe (
in diskette 1). You reboot and install diskette 1 to boot into Caldera DOS
and follow the instruction to insert diskette 2 & press anykey... It will
come up with Partition Magic 6 window (mouse driven) where you can do most of
the things in the installed Partition Magic in Windows...
Exit from the Partition Magic window . You enter DOS with the A:\> prompt.
Type ptedit & hit enter. You see the partition table editor window. You see
four rows numbered information. There's a type column, boot column, and
sector info on a partition. Look in the type column for a '0f' (extended-x)
and when you see it, highlight it and change it to '05' (standard extended),
click on the 'save changes' button. That's it!
Exit ptedit by clicking on the top X, you should get into the A:\> prompt.
Hit CTRL-ALT-DELETE to reboot and see if you get back your standard extended
partition and other missing, non-Microsoft logical drives...
Michael Iwaki
You have to understand what HPFS386 is. It's not so much a new
filesystem as it is an enhanced filesystem _driver_ that adds some
optional extensions to HPFS.
If you 'install' HPFS386, all you're doing is enabling the driver.
_IF_ (and only if) you don't use any of HPFS386's advanced features
like Local Security, or ACLs (which are created automatically if you
create any access rights at all), then you can 'revert' to plain HPFS
simply by returning to the old driver.
Under such normal use, the file system itself is not changed. It's
still an HPFS partition.
If you use ACLs or any of HPFS386's other physical extensions to HPFS,
_then_ the file system structure is changed. Extra information is
added to directory entries.
If you're not using any HPFS386-specific features, then the partition
is still pure HPFS on a structural level, and Partition Magic can handle
it just fine.
If you _are_ using ACLs and such, Partition Magic might be able to
handle the partition, but you'd lose all your ACLs. (Or it might choke;
I'm not sure which. Never tried.)
--
--------------------------
Alex Taylor
al...@eddie.cis.uoguelph.ca
--------------------------
> If you _are_ using ACLs and such, Partition Magic might be able to
> handle the partition, but you'd lose all your ACLs. (Or it might choke;
> I'm not sure which. Never tried.)
Attempting to resize (down) an HPFS386 partition: Error 1027
PowerQuest's advice: convert the HPFS386 partition to HPFS, resize,
convert it back to HPFS386. When I asked PQ how to do that, they said:
"
Date: Tue, 25 Apr 2000
Al, The only place I could point you to IBM for help.
If our program will not recognize the partition you will need to contact
OS/2
support for help.
Thank you,
Steven Park, MCP
steve...@powerquest.com"
Right. Big help, PQ. Remind me to upgrade -- in your dreams.
So: anyone have a clear, perhaps stepwise procedure to convert HPFS386
w/ACLs to HPFS? I assume PREPACL, BACKACC etc. are involved.
--
Regards,
Al S.
* Hillman & Rootes Group manuals online: http://asavage.fdns.net/Hillman
* Ford Falcon manuals online: http://FalconFAQ.fdns.net
This OS/2 system ("Tori", W4 FP15) uptime is 0 days 00:22 hours
> On Tue, 21 Aug 2001 14:37:11, al...@eddie.cis.uoguelph.ca (Alex Taylor)
> wrote:
>
> > If you _are_ using ACLs and such, Partition Magic might be able to
> > handle the partition, but you'd lose all your ACLs. (Or it might choke;
> > I'm not sure which. Never tried.)
>
> Attempting to resize (down) an HPFS386 partition: Error 1027
>
> PowerQuest's advice: convert the HPFS386 partition to HPFS, resize,
> convert it back to HPFS386. When I asked PQ how to do that, they said:
>
> "
> Date: Tue, 25 Apr 2000
>
> Al, The only place I could point you to IBM for help.
> If our program will not recognize the partition you will need to contact
> OS/2
> support for help.
>
> Thank you,
> Steven Park, MCP
> steve...@powerquest.com"
>
> Right. Big help, PQ. Remind me to upgrade -- in your dreams.
>
> So: anyone have a clear, perhaps stepwise procedure to convert HPFS386
> w/ACLs to HPFS? I assume PREPACL, BACKACC etc. are involved.
>
Correct me if I'm wrong, but you can upgrade HPFS to HPFS386, but not
the other way round if you want to keep the ACLs.
Maybe backup the partition, reformat with FDISK (LVM? haven't tried that),
do Partiion Magic on it, then restore from backup after making it HPFS386
again? And surely you'd need a backup method that respects NET.AUD,
ACLs, EAs, etc.
And if you need to resize adjacent HPFS386 partitions...well...you know.
Seems like it would be a bit of a dodgy recipe to me particularly if you need
to add or subtract partitions.
--
Best,
Erick Andrews
delete bogus to reply
The PREPACL program provided with LAN Server can be used to back up
(and remove) ACLs on an HPFS386 drive. (this "converts" it to standard
HPFS). You can then resize it with Partition Magic. Then you use
PREPACL to restore the ACLs that you backed up.
--
Lorne Sunley
Don't know how clear this info may be, but it's info I got. However, I never
did try to do this. This is from 2 different people.
1. Do you need ACLs (access control lists) to be saved?
If yes, then run BACKACC, and save ACLs in a file.
Look through WarpServer docs for more info and command line switches.
2. HPFS386 implementation put permission flags right into the file system, like
a regular file attributes - date, time, etc. As soon as you define the first
permission rule and apply changes to the file system, all file requests are
validated with the HPFS386 driver. Plain HPFS doesn't have such functionality,
and to access files using HPFS (not HPFS386!) you must remove permission
attributes. In order to remove permission flags, use PREPACL utility. Look
through WarpServer docs for more info and command line switches. After you
remove ACLs from your file system, you'll be able to access directories and
files. And now you can remove HPFS386 statement from your CONFIG.SYS.
3. Run PartitionMagic (or whatever Magician you like :-).
4. If you saved ACLs using BACKACC, now revert back HPFS386 statement into your
CONFIG.SYS and after reboot run RESTACC utility to re-apply permission flags to
your file system.
- - - - -
BACKACC only backs up the user ID file NET.ACC the ACL's are
embedded in the directory files and the data file. You have to
use PREPACL to back up the ACL's on an HPFS386 partition.
After the ACL's are backed up and removed with PREPACL.EXE you have
to remove the reference to the HPFS386.IFS in the config.sys file and
replace it with HPFS.IFS. Make sure your server software does not
start when the machine is re-booted.
When the machine is rebooted it is now running a normal HPFS partition
and you can access it with Partition Magic.
Make sure you back up ALL of the partition before you do this.
After the partition is resized, you can switch back to the HPFS386.IFS
and use PREPACL to restore the ACL's to the partition.
PREPACL is documented in the "Administrator Tasks" in the
LAN Server books.
- - - - -
--
Terry Norton
Connected with eComStation
http://www.eComstation.com/
> Maybe backup the partition, reformat with FDISK (LVM? haven't tried that),
That would be: reformat with..... FORMAT !!!
--
Bob Eager
rde at tavi.co.uk
PC Server 325; PS/2s 8595*3, 9595*3 (2*P60 + P90), 8535, 8570, 9556*2,
8580*6,
8557*2, 8550, 9577, 8530, P70, PC/AT..
> On Tue, 21 Aug 2001 20:06:47, eand...@bogusstar.net (Erick Andrews)
> wrote:
>
> > Maybe backup the partition, reformat with FDISK (LVM? haven't tried that),
>
> That would be: reformat with..... FORMAT !!!
>
Duh, sorry. I guess I had too much at my daughter's wedding!