The result: LINLOAD.EXE got loaded, but it was unable to load milo,
because the AlphaBios will set OSLOADFILENAME to a directory and not to
the file itself. (If I enter the complete Filename, the AlphaBios will
not even try to boot, because it is not a directory)
So I think, for the Alphabios a special linload.exe is needed, which
will boot something like OSLOADFILENAME\milo. Is this right, or am I
missing anything?
After reading the manual, I tried to change the firmware. I switched the
jumper to "Failsafe Boot Block Floppy" and booted it with a milo.dd
image. This seemed to work, the milo prompt came up, but if I enter
"show" or "boot ..." the system restarts (biosemulation and milo restart
from memory - not from disk)
Before it rebooted, it showed: "2.88MB Floppy detected" (1.44MB
installed), "No Floppy controller found", and exited with a panic in the
NCR 810 driver. I can't see it, because it's to fast.
I think, the devices are not correctly initialised when using this
firmware?
What else can I do? Where is my fault?
Or is the FAQ still true, that it is not possible to boot a XLT? But
then, what are the images for?
Joerg.
-- ================================o&o===================================== Joerg Rottland FZR rottland@fb9-ti.uni-duisburg.de Gerhard-Mercator Universitaet | http://www.fb9-ti.uni-duisburg.de/ FB9/Elektrotechnik - TI | Bismarckstr. 90 | Tel:+49 203 379 4224 D-47057 Duisburg | Fax:+49 203 379 4363