[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Elks Problem
From: Joseph Dunn ####@####.#### Date: 3 Jun 1999 22:43:46 -0000 Message-Id: <Pine.LNX.4.04.9906031737220.450-100000@zapper.dynip.com> On Thu, 3 Jun 1999, Ross Vandegrift wrote: > This one has been bugging me since ELKS *.67. I cannot for the life of me > figure out why I can't login using this setup. Luke: get curious like I > did - try to use your ELKS boot disks to boot a +386 machine. I found that > I still couldn't login there either, but it had a different problem. In > case your problem is different than mine, it has been suggested to me, on > this list, that init is spawning consoles and this somwhow hammers the > hardware. Changing that didn't help me at all, but you might want to try. > Anyhow, I'm still working on the problem, I'll let ya know if I find > anything cool... I have been able to boot ELKS on my overclocked 486 just fine, although when I hit CTRL-C ELKS displays a heart instead of stopping the program that I'm in. -Joseph Dunn | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |