On Sun, Jun 01, 2003 at 04:56:18PM +0200, Fred N. van Kempen wrote:
On Fri, 30 May 2003, Soeren Gust wrote:
The 2000 is tricky, in that its ROM implementation of
the MOP loader protocol is very picky about buffer
sizes during transfers, and since it has very space
to play with, transfers can fail, especially with
fast senders.
If I put some load (cat /dev/urandom | gzip -9 >/dev/null) onto the sender
machine even the big VXT.SYS image gets loaded successfully every time
so far.
If I put my
VS40X 4 plane color option board into the
machine it seems to crash when it has finished loading.
Are you sure the board is
OK? I don't have a 4-plane in
my machine, but know for sure it should work.
I am not completely sure, but the console works and the board does not
show any errors in the TEST 0. The machine went through several hands
until it reached me, but the story says that it was running as X
terminal in its first life. It could be thrown out because of a defect.
supported by
the VXT software? Or is it a firmware issue? My board has
version 1.4, are there newer versions available? Or even older version?
I believe
mine is 1.7 or so, so this could be an issue.. if the ROM
does not initialize the card right, you might get into trouble. Also,
you need at least 8 or 12MB of RAM in the machine, as the entire MOP
image gets loaded (and then expanded) in memory. It could well be
that your system crashes on memory limits while trying to decompress
the image and/or activating the color drivers.
Could you perhaps dump the ROM and send it to me? I do have 14MB RAM,
so thats not the problem.
If you need a reliable (even under Linux :) MOP
server, let me know.
Yes I am interested, can I download that somewhere?
Soeren