Date: 10 Apr 97 13:29:34 +0100
   From: Manfred Wagner <wagner@online-service.de>

   >loadbsd -t [other options]

   Neuer Shell-Prozeß 12
   12.Ram Disk:> loadbsd -p -b Store:netbsd
   Askboot...Using 16M FASTMEM at 0x3000000, 1M CHIPMEM
   Kernel at 022d4440, Fastmem used at 03000000
   loadbsd: Can't copy downwards yet.:
   12.Ram Disk:> 

It should be named "upwards", but otherwise you see the problem.

I must confess, that I compiled your loadbsd-MWSE this morning, but
forgot to upload it before leaving home. 

As a workaround, I suggest that you copy some large files to the RAM:
disk, until the machine is forced to load the kernel to segment 2,
like in your second try:

   loadbsd -t -b Store:netbsd
   Translated 01c00020 sz 007fffe0 to 01c00020 sz 007fffe0
   Translated 03000020 sz 00ffffe0 to 03000020 sz 00ffffe0
   Translated 00001000 sz 000ff000 to 00001000 sz 000ff000
   mem segment 1: start=01c00000 size=00800000 attribute=0005 pri=64
   mem segment 2: start=03000000 size=01000000 attribute=0005 pri=64
   mem segment 3: start=00000000 size=00100000 attribute=0703 pri=-10
   kernel size: 1226708
   Askboot...Using 16M FASTMEM at 0x3000000, 1M CHIPMEM
   *** Loading from 03ed45f0 to Fastmem 03000000 ***

What I don't understand at all, is why it is loaded to the upper
segment.  In loadbsd-2.14 and higher, there is a MEMF_REVERSE flag in
the AllocMem() responsible, which should force the initial kernel
image into the highest addressed available memory chunk of that size.


Regards,
	Ignatios Souvatzis