NASLite Network Attached Storage

So I set up my old P200 with two 80GB drives. I start it up with the NASLite-SMB floppy in it, but right after it gives its first message, "NASLite...", it sends a bunch of unintelligable messages to the console.

AX:0215
BX:1E00
CX:0001
DX:0100
0412

And it just sends that over and over and over and you get the idea. I have absolutely no idea what it's doing, but it deffinitely isn't doing what it's supposed to. I tested the floppy on a PII-300 with the same drives, and it worked fine. Everything started up and I could log in from both the machine and remotely over telnet. But the P200 is having major issues. Anybody have any idea as to what might be wrong?

That's a common bug with some old BIOS implementations. Check for a BIOS upgrade. On rare occasions a floppy may also cause the problem...

I've now tried over 20 different floppys (no joke - I have boxes of these things, sitting next to the boxes of cassette tapes). So now I have to figure out where to get an update for my BIOS:

AMIBIOS (C)1992 American Megatrens, Inc.
BIOS Version 1.00.03.BSOT

Anybody know where to get the update?

Looking at the BIOS boot message, is this a Gateway? If so, the BIOS updates are available on their website...

Is there a possibility of running it through a PXE boot?

I have same problem. Was it the Gateway bios? If so did you find a bios update?

I also had this problem in the following situation, and found a solution.

I had my NasLite running on an old Compaq (700MHz Athlon). I then moved the HDD and the floppy disk drive to a completely different modern system. The symptom that Agrajag9 describes happened.

I thought it had to do with the BIOS not properly supporting 1.7MB floppy. Notice that NEITHER the floppy disk DRIVE nor the floppy DISK changed.

After trying a bunch of things with the BIOS with no luck I booted Knoppix on the modern system and re-created the floppy (using the same physical floppy that worked before in that same floppy disk drive).

PROBLEM SOLVED !

Moral of the story: CREATE the floppy disk on the system that will boot from it !

While creating the diskfrom the machine that will eventually use it is one solution. However, I had this same problem and found it to be a bad floppy. So I guess what I am saying is that not every solution will fix everyones problem.