Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!rochester!udel!mmdf From: C0033003%DBSTU1.BITNET@cunyvm.cuny.edu Newsgroups: comp.os.minix Subject: re: system hanging after boot Message-ID: <1931@louie.udel.EDU> Date: 7 Apr 88 09:54:32 GMT Sender: mmdf@udel.EDU Lines: 46 Tony Goodloe writes: >Does anyone have any experience running Minix on a Tandy 1000? What do I >need to do to get Minix running? It will boot, but when I try to load >the root file system the computer hangs. Also, are there any special >considerations when using a hard disk on the 1000 with Minix? >Thanks for any help] I had exactly the same problem when bringing MINIX to my new ITT 80386 machine. So I posted this problem and got a response from Wes Peters (thanks Wes): >Date: Sat, 2 Apr 88 18:14:26 GMT >From: Barnacle Wes >Subject: Re: MINIX on ITT 386s >This is the same behavior I've noted when trying to boot Minix on two >different 386 machines: AMT 386, with 64K SRAM cache, and Acer 1100, >using interleaved RAM. I've even tried slowing them to 6 MHz - still >didn't work. We began tracing the problem, and decided it probably >lives in the BIOS. We have some NEC APC IV's here, 2 with Rev A BIOS, >and 2 with Rev B BIOS. The two with Rev B boot Minix without >problems, the two with Rev A act the same as the 386s. >When you press `=' to tell the Minix loader program to load Minix, it >makes a BIOS call to do something (.......) Apparently, >this BIOS call is where it dies. I think this BIOS call is only made >in the AT version of Minix. > Wes Peters If it's really this way it should not be a special problem of the TANDYs or ITT 80386s. Booting is done with those standard BIOS functions the same way like MS-DOS would be booted otherwise. If you type '=' after booting MINIX is started ( jump to 1536 ). On my machine ( ITT80386 ) the floppy-drive starts and keeps running all time until I reset. If the BIOS calls would be used it should still work? This looks like MINIX is waiting for something in its own floppy drivers. Maybe discrepancies in the disc-controller's registers? Any ideas? Detlef J. Schmidt C0033003 at dbstu1.bitnet computing center university of brunswick