Tried mainly with int-15 option (with and without allocating 1.4mb in himem to int-15 too) I also tried with keep none, undi and and all, but none of these options helped. I have tried some more things today, and have found that it's drvspace causing the problem. The floppy that I am imaging is a compressed floppy. I managed to change the scripting and fit what I needed onto a non-compressed floppy, that still loads drvspace.bin (though doesn't mount the floppy as it's uncompressed), and it works perfectly now. (I was told that to do what I'm doing (booting win98 off ramdisk with drvspace) that the floppy had to be compressed so that drvspace.bin is loaded in time, this is partly true, you can just load drvspace by drvspace.ini without having to compress the floppy) Apparently drvspace.bin is loaded into the top of concentional memory before config.sys is processed and then once config.sys is processed drvspace.bin is moved to the bottom of conventional memory. There are options using drvspace.sys in config.sys to control this movement and try and moveit to HMA etc. But none of the options resolved the problem. So the problem isn't resolved, just bypassed, which is good enough for me ! Thanks for your assistance ! .Andrew -----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Gero Kuhlmann Sent: 15 February 2004 18:56 To: email@example.com Subject: Re: Netboot ms-dos7 Hello, On Thu, 12 Feb 2004 03:59:57 +0100, Andrew White wrote: > I am 'trying' to get netboot to work with ms-dos7 (win 98), but seem > to be having memory problems. > [...] > My config.sys is > Device=himem.sys /testmem:off > Device=emm386.exe > Device=ifshlp.sys > Dos=high,umb > > I have tried devicehigh options and using int15 options on himem.sys > and mknbi-dos, but can't seem to get any further than hanging on the vlm. > > My nic is a 3com pcmcia 3c575b and I'm using ndis driver How exactly did you call mknbi-dos? You should _NOT_ use any of the 'keep' options, because that will leave the bootrom network driver attached to the network interface, and your network stack is probably not able to connect to it - but that's just a guess. I don't have any experience with Netware. gero. -- Gero Kuhlmann Tollenbrink 18 Groote Gracht 33 firstname.lastname@example.org 30659 Hannover 26723 Emden email@example.com 04921/997561 =========================================================================== This Mail was sent to netboot mailing list by: Gero Kuhlmann <firstname.lastname@example.org> To get help about this list, send a mail with 'help' as the only string in it's body to email@example.com. If you have problems with this list, send a mail to firstname.lastname@example.org. =========================================================================== This Mail was sent to netboot mailing list by: "Andrew White" <email@example.com> To get help about this list, send a mail with 'help' as the only string in it's body to firstname.lastname@example.org. If you have problems with this list, send a mail to email@example.com.
For requests or suggestions regarding this mailing list archive please write to firstname.lastname@example.org.