[PADS] Some issues using FIPS on the Libretto 100 from last meeting

[Mike Leone]

--8P1HSweYDcXXzwPJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

LeRoy Cressy (leroy@lrcressy.com) had this to say on 04/19/03 at 07:58:=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> http://osdev.neopages.net/docs/pdf/partitiontypes.pdf lists the=20
> different partition types and indicates that 0Eh is
>=20
> 0e  WIN95:  DOS-16bit FAT, LBA mapped
>=20
> From what I found out this type was only used on win95  also 0f was the=
=20
> win95 extended partition. =20

Not according to my FDISK. It (correctly) says I have no extended partition=
s,
only primary ones.

> Also these partitions would not work with DOS=20
> and DOS will report it as an unknown partition.

if I boot using a DOS disk, everything is
fine. I can access the C: drive, run programs, etc.

Or did you mean using a DOS 6.22 boot disk? My boot disk was created under
Win95 (which is DOS 7.0).

> So it seems that fips is not the problem but DOS does not even recognize=
=20
> a M$ partition which is normal.  I think that the solution would be to=20
> use a dos box within win95 which might work.

My Win95 FDISK recogonizes the partition just fine - it shows it as FAT16, =
active,
etc. No worries. It is the FDISK that comes with Win95, however.

It's FIPS that doesn't recognize the partition type.

> Everything I have found suggests to use partition magic since fips run=20
> on top of DOS and recognizes only what DOS sees.

My PM v5 boot disks use Caldera DOS v7; it does not recognize my C: drive
type. It's FDISK lists it as VFAT LBA, as you note above. But real MS DOS v7
has no difficulty with it.

PM, of course, like the joyous wonder that it is, had no problem resizing
it, bless it's little heart. :-) So now I have a 300M Win95 partition (with
125M free, in case I need to resize down some more), and 1697 free space on
the drive.

Once I resized it, BTW, FIPS started working ... however, PM had claimed an
inconsistency inthe boot record, which it fixed. The FIPS documentation said
to pay no attention to this "error", as it was a normal warning message.

Also, PM changed the sector size from 32K to 8K - maybe FIPS didn't like 32K
sectors. Who knows?

In any event, it looks like it's ready to do the install at the next
meeting.

BTW, please reply to the list, not just to me.=20


--8P1HSweYDcXXzwPJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+oVNMmrQe9lqlvN8RAvMrAJ43uOFnumCHIk0cLN5nQlC5/u2JhwCdHT/k
mTghY+Er6T3TuUNufvkoMLI=
=bvLE
-----END PGP SIGNATURE-----

--8P1HSweYDcXXzwPJ--