Text 81, 92 rader
Skriven 2006-05-14 10:40:46 av Peter Knapper (3:772/1.10)
     Kommentar till text 77 av Sarah Nunez (1:130/604)
Ärende: Install trouble
=======================
Hi Sarah,

 HR> I've given up on FAT32 years ago because crap. 

I used the FAT32 driver to access a USB Camera Memory card for a while, however
while the FAT32 driver does seem work fine with Hard drives, there are still
issues when using it with Removable Media (IE the USB Camera Memory card must
be partioned or you have to use a DANI work-around). Neither of those options
worked well for me, however I ran across another method for transferring Camera
Files that needs NOTHING other than the "standard" USB drivers and that is
working perfect for me without any FAT32, Partitioning of the Flash Card or
"special" USB or Camera drivers required...


 SN> I believe there's an HPFS driver for Windoze, 

There was... for NT3.5 & 4, however MS either did not include it, or possibly
just not INSTALL it with their later OS's. I think it was on a W2K system I
used once, but not sure it came as standard...


 SN> Besides, I haven't yet figured out how to update the Linux kernel 
 SN> to also read HPFS drives.  

Have you investgated JFS (I am using it with eCS 1.2MR)? I am pretty sure that
JFS is also available for Linux. I don't think its available on any Win
platforms though, although it could be there, I think the Linux source is
available if someone wanted to try it...


 SN> That leaves me with only FAT32, such as it is.

There is one other rather remote option and that is using it as a NETWORK
drive, but that would take more resources and is probably not applicable to
your needs.


 HR> OS/2 before 4.51 is really unable to get installed outside the 1024
 HR> zylinder limit.

 SN> This is 4.52, but even so, I'm trying to install to a 
 SN> partition that IS within the 1024-cylinder limit.

I actually disagree with Herbert's comment about that... with qualifications -

 HR> There can only one BM on the whole system. When you have BM on
 HR> disk 2 you must remove it from there and you must reboot to get that
 HR> in effect before you can install BM on disk 1.

I have run with BM installed to both SCSI HD's since OS/2 v2.1 days without
issue, so there are situations where it CAN be done. At least it has worked
fine for me up until I started using LVM with eCS 1.2MR. Now I did have some
funnies with a 2 x HD and 2 x BM's and installing eCS (on the first Disk), and
I ended up removing BM from the second HD to get things to work right, so I
dont know if that relates to what Herbert is suggesting or not. Its possibly
more an LVM specific issue...

I have NEVER booted from DRIVE 2 (I never had a need), HOWEVER I have booted
OS/2 from my SCSI drive, and had an IDE drive that was NOT enabled or
configured in the BIOS, come up as the THIRD HD. As long as the IDE driver is
later on in Config.Sys, this seems to work fine. It all comes down to the ORDER
the drives are found by the BIOS and how that ORDER relates to the driver load
order within OS/2.

 SN> Here's how I'm trying to do it (both drives are 160GiB):

 SN> disk 0:

 SN> - BM (7.8 MeB = 1 cylinder)
 SN> - Win2K (4 GiB FAT32)
 SN> - Win Programs (~17 GiB FAT32)
 SN> - remainder divided into 32 GiB data partitions

 SN> disk 1:

 SN> - OS/2 (2 GiB HPFS)
 SN> - Linux boot
 SN> - Linux swap
 SN> - Linux root
 SN> - OS/2 Programs (~10 GiB HPFS)
 SN> - remainder divided into 32 GiB data partitions

Can you add partition Type info (Primary or Logical paartition) against those?
That might explain some of the odd things you are seeing... Plus also advise if
LVM is involved and if so are the Partitions marked as, compatibility volumes
or "Native / LVM advanced" partitions?

Thanks.............pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)