Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SYSEDIT????

0 views
Skip to first unread message

Robert G Pielke

unread,
Feb 21, 1995, 5:20:35 PM2/21/95
to
For some reason, I can not longer access the AUTOEXEC.BAT file in
SYSEDIT. Anyone have an idea how I can get it back?? (BTW, I can access
it in all the other ususal ways, i.e., Write, Notepad, File Mgr., and EDIT.)

Robert G. Pielke
Ed/Pub OFFBEAT PRESS
Professor of Philosophy
Logic/Ethics/Sex/Drugs/Rock & Roll
El Camino College
Torrance, CA 90506

Joe Morris

unread,
Feb 22, 1995, 8:56:11 AM2/22/95
to
Robert G Pielke <rpi...@EIS.CALSTATE.EDU> writes:

>For some reason, I can not longer access the AUTOEXEC.BAT file in
>SYSEDIT. Anyone have an idea how I can get it back?? (BTW, I can access
>it in all the other ususal ways, i.e., Write, Notepad, File Mgr., and EDIT.)

The probable reason is that the combined size of AUTOEXEC.BAT, CONFIG.SYS,
WIN.INI, and SYSTEM.INI has grown and now exceeds 64K bytes. I had
the same problem several years ago when I was using PCL fonts and had
umpteen lines in the [printer] sections of WIN.INI for each typeface
and each printer.

Joe Morris / MITRE

Walter Knopf

unread,
Feb 24, 1995, 11:33:33 PM2/24/95
to
In article Robert G Pielke <rpi...@EIS.CALSTATE.EDU> writes:

>For some reason, I can not longer access the AUTOEXEC.BAT file in
>SYSEDIT. Anyone have an idea how I can get it back?? (BTW, I can access
>it in all the other ususal ways, i.e., Write, Notepad, File Mgr., and EDIT.)

SYSEDIT looks for it as c:\autoexec.bat. Either you set your autoexec hidden,
moved it, or the string in sysedit got corrupted. in which case you could re-
install sysedit or use a hex editor to fix it.

Walt

0 new messages