problem installing from MSDOS partition

Been to Google, FAQ, etc.

As part of my exhaustive work in "How to Install OpenBSD," I tried installing from a MSDOS partition where I had NT 4.0 installed. Thanks to the serial console, here are my results:

[blah blah blah deleted...]

Sets can be located on a (m)ounted filesystem; a (c)drom, (d)isk or (t)ape device; or a (f)tp, (n)fs or (h)ttp server. Where are the install sets you want to use? (m, c, f, etc.) d Available disks are: sd0 sd1 wd0.
Which one contains the install sets? (or done) [sd0] wd0

The following partitions have been found on wd0:

1. 1024002 8193150 4.2BSD 1024 8192 16 # (Cyl. 8128*- 9143)
2. 1208592 9217152 swap # (Cyl. 9144 - 10342)
3. 39179952 0 unused 0 0 # (Cyl. 0 - 38868)
4. 12582864 10425744 4.2BSD 1024 8192 16 # (Cyl. 10343 - 22825)
5. 2097648 23008608 4.2BSD 1024 8192 16 # (Cyl. 22826 - 24906)
6. 14060214 25106256 4.2BSD 1024 8192 16 # (Cyl. 24907 - 38855*)
7. 8193087 63 MSDOS # (Cyl. 0*- 8128*)

Partition? [a] i

The following filesystem types are supported: default (deduced from the disklabel) ffs
msdos
Which filesystem type? [default] msdos
Enter the pathname where the sets are stored (or '?') obsd No OpenBSD 3.2 install sets were found in

    '/mnt2/obsd'

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related openbsd.org Links advocacy announce bugs ipv6 misc ports ports-changes security-announce smp source-changes tech Request more information about Pantek

Search for other *.tar.gz and *.tgz files? [y]!

A bit of searching around led me to what I suspect is the problem:

# ls /mnt2/OBSD

BASE32.TGZ   CKSUM        FLOPPYC3.FS  INSTALL.I38  MAN32.TGZ    XFONT32.TGZ
BOOT.CAT     COMP32.TGZ   GAME32.TGZ   INSTALL.LIN  MD5          XSERV32.TGZ
BSD          ETC32.TGZ    INSTALL.ATA  INSTALL.MBR  MISC32.TGZ   XSHARE32.TGZ
BSD.RD       FLOPPY32.FS  INSTALL.CHS  INSTALL.OS2  TRANS.TBL
CDROM32.FS   FLOPPYB3.FS  INSTALL.DBR  INSTALL.PT   XBASE32.TGZ

It's a MSDOS filesystem, and all the files are in upper case, of course. From reading install.sub, it *appears* that the install script will not recognize upper-case names.

Is anyone aware of a workaround? Or is something else going on?

Thanks,
==ml

-- 
Michael Lucas		mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org
http://www.oreillynet.com/pub/q/Big_Scary_Daemons

           Absolute BSD:   
http://www.AbsoluteBSD.com/