is this with the very latest 1.4 sysinst?

"John F. Woods" <jfw@jfwhome.funhouse.com> writes:

> [Actually the floppy drive wasn't dead, I was using /dev/rfd0d because of a
> brain bubble...]
> 
> I think I've tracked down the "No operating system" problem to the traditional
> BIOS-geometry/fdisk-geometry disagreement.  That seems to cut the list of
> problems down to
> 
> 	* misleading or broken partition editor
> 	* unexplained lockup of sysinst output
> 
> The install ramdisk is not an ideal environment for debugging, but I'll see
> if I can nail down what is going wrong with sysinst.