Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

PC DOS 2000 Memory Problems

Original Message
Name: rkeldos
Date: May 27, 2007 at 20:05:05 Pacific
Subject: PC DOS 2000 Memory Problems
OS: IMB PC DOS 2000
CPU/Ram: P4 3.2GHz/2Gb RAM
Comment:
Having a problem with IBM PC DOS 2000.

When I insert the following lines into config.sys:

device=c:\dos\himem.sys
device=c:\dos\emm386.exe noems
dos=high,umb

It deletes itself or corrupts itself badly after a few file operations (copy/move, etc).

The machine is ~2.5 years old. 3.2 GHz P4 with 2 gigs RAM.

DOS is being installed on a 2 gig partition at the start of the drive.

Anyone got any ideas?


Report Offensive Message For Removal


Response Number 1
Name: Santa
Date: May 27, 2007 at 22:35:12 Pacific
Subject: PC DOS 2000 Memory Problems
Reply: (edit)
PC-DOS has a built in memory configuration tool, run RAMSETUP.EXE from the command line.

http://www.redbooks.ibm.com/abstrac...


Report Offensive Follow Up For Removal

Response Number 2
Name: rkeldos
Date: May 28, 2007 at 03:17:36 Pacific
Subject: PC DOS 2000 Memory Problems
Reply: (edit)
Thanks for the reply.

I ran ramsetup, and it still ate itself. This time it was a bit quicker.

Is it a problem that I have 2Gb of RAM installed in this machine?

MS-DOS doesn't seem to have any problems. It's just PC-DOS giving me these headaches.


Report Offensive Follow Up For Removal

Response Number 3
Name: Santa
Date: May 28, 2007 at 03:32:36 Pacific
Subject: PC DOS 2000 Memory Problems
Reply: (edit)
RAMSETUP configures the settings for you, therefore no need to manually tweak!

Report Offensive Follow Up For Removal

Response Number 4
Name: rkeldos
Date: May 28, 2007 at 04:02:06 Pacific
Subject: PC DOS 2000 Memory Problems
Reply: (edit)
I know. I didn't manually tweak anything.

It still corrupted itself.


Report Offensive Follow Up For Removal

Response Number 5
Name: Santa
Date: May 28, 2007 at 04:58:38 Pacific
Subject: PC DOS 2000 Memory Problems
Reply: (edit)
http://www.pldos.pl/pcdos/psm951a.htm


The only trick is to look in BIOS and see if it has an option for less than 64MB Mem OS/2...


Report Offensive Follow Up For Removal


Response Number 6
Name: Lupin3rd
Date: May 28, 2007 at 06:53:03 Pacific
Subject: PC DOS 2000 Memory Problems
Reply: (edit)
MS-DOS 6.X only recognises 64 meg of ram that's why that works fine.

Quatermass O.B.E


Report Offensive Follow Up For Removal

Response Number 7
Name: rkeldos
Date: May 28, 2007 at 16:29:39 Pacific
Subject: PC DOS 2000 Memory Problems
Reply: (edit)
Thank you.

I'll have a look through my BIOS settings. Hopefully there's something there.

Failing that, are there any patches available for PC DOS to allow it to work on machines with more than 64mb RAM?


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: PC DOS 2000 Memory Problems

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




DSHUB24 Connection Problems

need help with dsl and dial up

novel 3.12

help mandriva install last straw!

Icon Scaling in Explorer Bar


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC