Maker tech hub — AI · 3D print · Pi · ESP32 · plus the classic tech archive.

Free ESP32 kit · Books · Network Ninja · Archive

Classic tech archive. From the original averyjparker.com tech blog — historical context; pair with modern guides where noted. Full archive · Maker projects · Network Ninja

Classic tip · Linux

Strange Novell Server error

I ran into strange problems accessing a shared Novell Netware (5.0) folder. Everytime the folder was attempted to be accessed from multiple machines the window would freeze and if you waited long eno…

Written by

Avery J. Parker

IT veteran, maker educator, and author of Network Ninja, 3D Printing Mastery, and AI Workflow Mastery. Business IT: Diversified Tech Solutions.

I ran into strange problems accessing a shared Novell Netware (5.0) folder. Everytime the folder was attempted to be accessed from multiple machines the window would freeze and if you waited long enough, there would be an error message along the lines of "Netware Alert Message"... NIOS.NLM

Call to NIOS page unlock by module unknown failed Address 0x05650016, length 0x00700465 and then according to what I was told, ctrl-enter was instructed to clear the message and the machine rebooted.


This was tried from several machines and logins, all with permission to access the folder. So, I thought I'd try browsing it from the netware console... "load cpqfm" loaded the compaq file manager and I started browsing to the folder, and >>>> it hung... at this point I was thinking that we might be seeing early hard drive read problems, so I returned to the netware console and attempted to unload the cpqfm ... at this point the console hung as well and stopped receiving keyboard input (beeping with every button press..)

So, I informed everyone of a pending reboot. What's funny is that after the reboot everything was accessible. I don't know much about netware, but I thought this might be a warning sign of hard drive failure. They're in process of abandoning the old fileserver anyway, so they'll be copying files off in the next couple of weeks anyway.

After things turned up working after the next reboot, I started wondering if maybe a lock file of some sort had been stranded (or written to a bad area of disk?) Anyway, since a reboot has at least temporarily solved, thought it was worth mentioning. (Given that I couldn't find much in the way of good google leads....)