[syslinux] MEMDISK reset computer with NW Client32

Tue Oct 3 11:53:03 PDT 2006

Hi Petr,

  It sounds like you might be using the standard Microsoft (tm) ramdisk.sys's with NetWare Client 32 to logon from DOS?  I would suggest trying Franck Uberto's excellent XMSDSK.EXE instead and seeing if that helps you with your problem:

  http://www.simtel.net/pub/pd/4825.html  (I would suggest downloading from here)
  http://www.geocities.com/politalk/rmdrv/fu_rd19i.htm  (this provides a useful file list)

  From what you have described it sounds like your problem may be with the DOS NW client over-writing something else in memory.  I would look into this by booting without loading the NW client and typing the DOS command "mem/d | more" to see where the address of the ramdisk is going.  Then check your net.cfg etc to see if you are loading your VLM's etc into memory areas already used by the ramdisk or memdisk etc.

  Tip: you can also visually see what is located where in "low" DOS memory by using ramspy:  http://www.programmersheaven.com/download/15858/download.aspx

  Regards Richard

Petr Olivka <petr.olivka at vsb.cz> wrote:
  Hi!

I have problem with MEMDISK, because when I load modules in NW Client32 
using NIOS.EXE commands, computer is restarted :-( Not everytime, but 
manytimes.

The problem is with MSDOS 5.0, 6.22 and FreeDOS too. 

But when I create in DOS another RAMDISK and copy all data from MEMDISK 
to new RAMDISK and change settings and PATH to new ramdisk, all work fine.
Directly from floppy or from HD all work fine too. But two ramdisk is not 
good situation.

Does anybody have some experiences, how to debug this problem? I hope, i 
will be certainly some little error in asm. 

poli

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

---------------------------------
 All New Yahoo! Mail – Tired of Vi at gr@! come-ons? Let our SpamGuard protect you.