Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!uunet!mcsun!hp4nl!svin02!wsinis03!debra
From: debra@wsinis03.info.win.tue.nl (Paul de Bra)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO UNIX 3.2.2 and Micronics 486
Message-ID: <1662@svin02.info.win.tue.nl>
Date: 4 Jan 91 09:50:43 GMT
References: <1990Dec30.002048.8203@world.std.com> <298@shograf.UUCP>
Sender: news@svin02.info.win.tue.nl
Reply-To: debra@info.win.tue.nl
Organization: Eindhoven University of Technology, The Netherlands
Lines: 20

In article <298@shograf.UUCP> jim@shograf.UUCP (jim morris) writes:
>...
>I have had the same problem on the Club AT Hawk 3, 33Mhz 486.
>It won't boot unless you start in non-turbo mode. After it has booted
>everything (except TCP/IP) works fine when switched to turbo mode.
>...

Sounds like the old boot/speed problem again.
A vanilla sVr3.1 unix would not boot on my 25Mhz 386 box unless I slowed
it down to 8Mhz. sVr3.2 solved this problem.
Since the boot program cannot use real timers or something like that
to wait for asynchronous events it just loops a while, and on a 33Mhz 486
this loop may be over too soon for whatever it is the boot program
wants to wait for.

Once Unix has booted I could switch to 25Mhz with sVr3.1 and everything
was fine. Your problem is very similar...

Paul.
(debra@research.att.com, debra@win.tue.nl)