DOS6.22 problem

[Arthur]

yes / no its not missing a colon - when I posted it here showed a instead of :OFF




not sure why it's repaeated - that is how it is on the other cnc machine.

P6M is the software needed to run the CNC machine.

it's rem's out so that I don't load it while I piss about with the network

I seem to recall XMS defaults to :ON, so if himem gets corrupted or is too tight you can save a few kilobytes with :OFF. It'd bomb without the colon.

 

[MrGray]

I very vaguely recall something about emm386.exe solving a lot of memory issues, but then that was a few decades ago...

 

[Arthur]

I very vaguely recall something about emm386.exe solving a lot of memory issues, but then that was a few decades ago...

Memories about memory battles.

There were two rival "standards" for getting above 640kB: Extended and Expanded. XMS and EMS. OP is battling with XNS. Lucky he doesn't have to set DIP switches on the mobo.

 

[spiff]

ok after writing in the following line

DEVICE=HIMEM.SYS /TESTMEM:OFF

I get a error message - BAD OR MISSING HIMEM.SYS
ERROR IN CONFIG.SYS LINE 1

 

[Arthur]

Then himem.sys isn't in the defined system path. Put it there.

 

[spiff]

also get the folowing

EMM386.EXE NOT INSTALLED - EXM MANAGER NOT PRESENT

 

[dabean]

ok after writing in the following line

I get a error message - BAD OR MISSING HIMEM.SYS
ERROR IN CONFIG.SYS LINE 1

You're missing the path. It should be C:\DOS\HIMEM.SYS or whatever.

Did you try running memmaker? It's part of DOS since 6.0

 

[Blue Shirt]

ok after writing in the following line

I get a error message - BAD OR MISSING HIMEM.SYS
ERROR IN CONFIG.SYS LINE 1

Its looking for himem.sys in the wrong directory.

 

[The_Librarian]

ok after writing in the following line

I get a error message - BAD OR MISSING HIMEM.SYS
ERROR IN CONFIG.SYS LINE 1

Try

DEVICE=C:\DOS\HIMEM.SYS wafflewafflewaffle ,(am on a phablet atm)

 

[spiff]

Then himem.sys isn't in the defined system path. Put it there.

right so where must all these file go?

autoexec.bat?

config,sys ?

command.com

emm368.exe?

himem.sys?

root dir or c:\dos

 

[Arthur]

autoexec.bat and config.sys in root. The rest can be in DOS system path which you can set with PATH command, or use the full filespec.

Wife is calling me to lunch to leaving you in more capable hands. Good luck.

Quick Edit: Command.com should be in root already, along with its hidden sys file.

 

[spiff]

autoexec.bat and config.sys in root. The rest can be in DOS system path which you can set with PATH command, or use the full filespec.

Wife is calling me to lunch to leaving you in more capable hands. Good luck.

Quick Edit: Command.com should be in root already, along with its hidden sys file.

great thanks - got that sorted.

 

[spiff]

PROGRESS!!

so it boots up now without any memory errors or missing or bad files etc.

now it's asking to log onto network but it's missing the drive!

something about the LASTDRIVE command inthe config.sys file

it was there before - LASTDRIVE=Z

 

[Sinbad]

Hehe. Ja, edlin will take too long to figure out.

jesus I just had flashbacks


Thinking back on it, edlin is probably the root cause for me loving vi

 

[Kilgore_Trout_Redux]

This thread is a thing of beauty. Brings a tear to my eye.

 

[Sinbad]

This thread is a thing of beauty. Brings a tear to my eye.

My uncle who lives in the UK brought me this as a christmas present when he came to visit in the late eighties...

 

[The_Librarian]

Ah, on a PC now...

By default. CONFIG.SYS does not have a PATH command (unless you're using OS/2) so you will have to use the full pathname of the device driver, for example
C:\DOS\EMM386.EXE
C:\DOS\NOSMOKE.EXE
C:\DOS\HIMEM.SYS

The PATH= command resides within the AUTOEXEC.BAT file, and this tells DOS in which directories to look for files if it is not present in the root
So, for example, you will have (when doing a DIR)
C:\DOS
C:\MENU
C:\MYPROG
C:\ACAD

and the PATH then will be
PATH=C:\DOS;C:\MENU

Thus DOS knows it will need to look into the DOS and MENU directories if any program is called, before returning with a Bad Command or File Name error.

But I digress

When networking with DOS, the LASTDRIVE=Z: need to be added to the CONFIG.SYS file (usually the last entry) before the NDIS (or network) drivers

Any chance of getting the contents of the original CONFIG.SYS and AUTOEXEC.BAT off from the original hard drive, even if it means slaving that drive into the CNC PC?

 

[The_Librarian]

My uncle who lives in the UK brought me this as a christmas present when he came to visit in the late eighties...

Oooohhhh... I played around with ANSI.SYS and colored MS-DOS prompts

 

[The_Librarian]

hehehe, getting flashbacks from creating Novell 2.2 and 3.12 remote boot images...

and editing config.sys+autoexec.bat for max memory, then creating the boot image, copying to the server, rebooting the workstation, running MEM/c etc until you get a working install with maximal amount of RAM...

...and, of course, finding a working boot ROM for the NE2000 NIC's...

was the days

FWIW prior to Novell 3.12 you did not need a lastdrive=z statement in config.sys, only with Novell 4 (and newer) did you need a lastdrive=z (and the endless hassles of getting enough free RAM for your application...)

 

[spiff]

ok guys some more progress

solved the lastdrive issue

it boots up alright now except now it's say - the computer name specified in the network path cannot be located

*: connected to \\*********\cnc2

I need to change the CNC2 > CNC1 - but when I run the NET.EXE command it says not enough memory again?