Remember, each post is a microcosm on its own. If you had some dual boot and we destroy such in the repair, I wouldn't know about this.
Bob
![]() | Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years. Thanks, CNET Support |
Bob,
still need my Me restored
any new ideas how to get that cursor back?
and I was unable to have the safe mode work
Discussion is locked
Bob,
I used the Diagnostic Setup option (second in the msconfig applet), the computer got into what looks like a safe mode (but there are no safe modes in the corners)
and...
there was the cursor!
going back to normal boot, its gone again!
not sure I understand your Q
anyway, checked all the boxes except the first one
and got a (almost!) fully functional (incl the cursor) OS, but a gray screen
are we close?
Use notepad and copy/paste it as a response.
Bob
[boot]
system.drv=system.drv
drivers=mmsystem.dll
user.exe=user.exe
gdi.exe=gdi.exe
sound.drv=mmsound.drv
dibeng.drv=dibeng.dll
comm.drv=comm.drv
mouse.drv=mouse.drv
keyboard.drv=keyboard.drv
shell=Explorer.exe
*DisplayFallback=0
[386Enh]
ebios=*ebios
device=*vshare
device=*dynapage
mouse=*vmouse, msmouse.vxd
device=*vcd
device=*vpd
device=*int13
woafont=dosapp.fon
keyboard=*vkd
display=*vdd,*vflatd
[drivers]
wavemapper=*.drv
MSACM.imaadpcm=*.acm
MSACM.msadpcm=*.acm
wave=mmsystem.dll
midi=mmsystem.dll
[mci]
cdaudio=mcicda.drv
sequencer=mciseq.drv
waveaudio=mciwave.drv
avivideo=mciavi.drv
videodisc=mcipionr.drv
vcr=mcivisca.drv
[drivers32]
MSACM.imaadpcm=imaadp32.acm
MSACM.msadpcm=msadp32.acm
MSACM.msgsm610=msgsm32.acm
MSACM.msg711=msg711.acm
MSACM.trspch=tssoft32.acm
vidc.CVID=iccvid.dll
VIDC.IV31=ir32_32.dll
VIDC.IV32=ir32_32.dll
vidc.MSVC=msvidc32.dll
VIDC.MRLE=msrle32.dll
msacm.lhacm=lhacm.acm
[TTFontDimenCache]
0 12=5 12
0 13=6 12
0 14=7 14
0 15=7 15
0 16=8 16
0 18=10 18
0 20=10 20
0 22=12 22
Since the MSCONFIG and don't process SYSTEM.INI works (correct me if I read that reply wrong), you can take your current \Windows\System.ini and edit it to disable lines inside to find what item it was.
The supplied System.ini looks more like what I would see if Windows ME was in the don't process SYSTEM.INI with MSCONFIG rather than the real one. It's another Microsoft'ism that you'll have to let MSCONFIG not be in its selective startup and boot up in ME to get the files to flip back into their former content.
But here's how to COMMENT or REMARK out a System.ini line. Example follows.
msacm.lhacm=lhacm.acm
is remarked out by add the ; character.
;msacm.lhacm=lhacm.acm
Bob
sorry Bob
I don't quite understand what is it that I have to do,
could you be more specific?
also, the title says: DO NOT EDIT THIS FILE!
Please don't leave out such details.
http://reviews.cnet.com/5208-6141-0.html?forumID=8&threadID=10785&messageID=124607 didn't list that line or I would KNOW that you still had MSCONFIG set to it's diagnostic/selective settings.
But I noted that in my reply.
So with that out of the way, please share the real SYSTEM.INI that you see when not in a MSCONFIG selective startup.
Bob
Just noticed
msconfig system.ini tab, 3 lines (with checked boxes), are complete trash!
guess they are corrupted
need to be rewritten?!
Something must be unclear with my request.
Can you help me ask this in a clear and simple manner?
From what I can tell, we could have found the issue a day ago, if the SYSTEM.INI file was revealed.
If you can't share it, that's fine, but come right out and tell the forum you can't do that.
Best of luck fixing it.
Bob
Bob come-one
this stuff is completely new to me
I am ready to do whatever you ask me to, in order to
solve the problem