I was merging partitions using Partiion Magic 8 when i recieved error message saying there is an error in line 1 of my config.sys file,and that himem.sys was missing or corrupted. I wanted to edit it but i get the bad command error.

Not much to go on - how are you trying to edit it? Is Windows still in operation?

Why don't they make computers that will do what we think we want them to do?

Report Offensive Follow Up For Removal

... hmm - I guess not if himem.sys is 'missing'

Ok - try

c:\windows\command\edit c:\config.sys

although I suspect there are other issues. Sounds like there is no path information - possibly MSDOS.SYS is not all it should be

Why don't they make computers that will do what we think we want them to do?

Report Offensive Follow Up For Removal

Try
A:\>attrib -r -s -h config.sys
and then try editing it.

Change it back when done using +r +s +h.

Bryan

Did Partition Magic complete the merge?

Did you run the "remapping" utility after the merge so programs/files are "pointed" to their proper new locations?

Normally (especially with 95, 98, & up) himem.sys shouldn't even be called from config.sys.

The machine i am working on had one drive partitioned into 15 diferent logical drives. I am not sure that the drive remapping took place, the last merge operation was running in DOS. I then got these errors:
Device=E:\windows\himem.sys
missing or corrupt. There is an error in line 1 of the config.sys file
Device=E\windows\emm386.exe
missing or corrupt. There is an error in line 2 of the config.sys file
Device=E:\windows\ifshlp.sys
missing or corrupt.
I have been stuck since then. Is it possible that the path references are wrong?

Normally, Windows will install itself and the DOS files on C:, although other arrangements are possible. MSDOS.SYS contains Windows path info - config.sys isn't required for Win9x

"Is it possible that the path references are wrong?"

Well, sure - are they? Do the referenced files exist at the specified locations?

Your configuration sounds unusual (to say the least), and it's a little hard to fill in the blanks. Maybe if you could explain how you expected the disk to be restructured, it might be possible to determine what's gone wrong.

Why don't they make computers that will do what we think we want them to do?

Report Offensive Follow Up For Removal

"Well, sure - are they? Do the referenced files exist at the specified locations?"

AND:

"Your configuration sounds unusual (to say the least), and it's a little hard to fill in the blanks. Maybe if you could explain how you expected the disk to be restructured, it might be possible to determine what's gone wrong."

Yeah, I was going to suggest running EDIT to look at your msdos.sys and config.sys as jboy outlined above (c:\windows\command\edit c:\config.sys), but if these programs/directories/files have been "moved" by P.M., the paths to same probably won't match anymore.

Just to clarify, I gather you're not getting into windows now, correct?

If you can explain how the disk has been restructured it would help a lot. If it helps, I can provide you with an old DOS 16 bit program that will find files under DOS 7.1.