 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows Me / System Tools / March 2006cmdninst and commctrl error
I have a gateway running windows ME. I tried to download a driver for a new epson printer. It kept stopping right at end of installation with cmdninst error. Now when I reboot I get cmdninst. I close it (ignore does nothing) and it says commctrl will now close. back to the blue screen. I was able to get into safe mode. I tried the microsoft support method of disabling various devices and I deleted everything epson in the add/delete programs area. (except a printer utility that the computer won't let me delete). I still come up to a blue screen. Nothing in device manager seems out of order. I also tried renaming cmdninst and extracting another one from a cab file into the system folder. That didn't work either. I have a recovery disk but not a windows ME disk. Does anyone have any other ideas? > Does anyone have any other ideas? Boot to Safe Mode and use System Restore and roll your PC back to the state it was in before you attempted to install the Epson driver.  SignatureMike Maltby mike.maltby@gmail.com > I have a gateway running windows ME. I tried to download a driver for > a new epson printer. It kept stopping right at end of installation [quoted text clipped - 8 lines] > into the system folder. That didn't work either. I have a recovery > disk but not a windows ME disk. Does anyone have any other ideas? >> Does anyone have any other ideas? > [quoted text clipped - 5 lines] >> into the system folder. That didn't work either. I have a recovery >> disk but not a windows ME disk. Does anyone have any other ideas? I tried that too but the earliest restore date is after I tried to install the printer. irishmidget asked :- > ... Does anyone have any other ideas? Not really but... You say that you downloaded a driver for your (new?) Epson printer - wasn't one supplied with the printer? Are you sure that the one you downloaded is the correct (and latest) one for WinMe. Although not specifically related to Epson printers/drivers, the following KB article *may* point you towards the problem/solution :- "Cmdninst Caused an Invalid Page Fault" Error Message While You Upgrade to Windows Millennium Edition http://support.microsoft.com/kb/277994/en-us Mart >I have a gateway running windows ME. I tried to download a driver for a new > epson printer. It kept stopping right at end of installation with cmdninst [quoted text clipped - 11 lines] > a > windows ME disk. Does anyone have any other ideas? >irishmidget asked :- > [quoted text clipped - 18 lines] >> a >> windows ME disk. Does anyone have any other ideas? The supplied disk gave me an error so I called Epson and they had me download one specifically for Me and that printer which is when the cmdninst thing started. Ican't really even try to install anything at this point until I can get rid of the cmdninst error as I'm in safe mode. As your SR points (pre-install of printer) have gone (as per your reply to Mike) you *might* still be able to run scanreg /restore and retrieve a registry that is 'pre' the install (last 5 dates should be offered) :- Start | Run and type "scanreg /restore" (no quotes and note the space between the g and /) Oh! and maybe ... whilst you are in Safe Mode, take a look at Start | Settings | Printers and see if any sign of the printer there, which you can remove/delete. Also, take a look in Device Manager and look for any yellow exclamation marks (bangs) and delete/remove them. Reboot and see if that gets rid of the cmdninst error. Mart >>irishmidget asked :- >> [quoted text clipped - 28 lines] > can > get rid of the cmdninst error as I'm in safe mode. BTW - Sorry if a daft question, but... You did remember to physically disconnect the printer before trying to troubleshoot ? Mart > As your SR points (pre-install of printer) have gone (as per your reply to > Mike) you *might* still be able to run scanreg /restore and retrieve a [quoted text clipped - 44 lines] >> can >> get rid of the cmdninst error as I'm in safe mode. >BTW - Sorry if a daft question, but... You did remember to physically >disconnect the printer before trying to troubleshoot ? [quoted text clipped - 6 lines] >>> can >>> get rid of the cmdninst error as I'm in safe mode. Yes I disconnected the USB cable. I looked at scanreg /restore (thanks for the suggestion)but it takes me back a few years which might be when my son crashed it with a virus so I guess I would use that as a last resort. I might try to restore to the original error before I tried anything and see what I can do. The weird thing is that there was never any problem in device manager even though everyone says the answer should be there. The only printer in my printer setting is something for adobe. Something for the epson does show up in my misconfig--start up list though so I unchecked that . didn't help though. I guess I'm just rusty at all this--I should have remembered to set a restore point before I tried to add theprinter. Lesson learned I guess. irishmidget wrote :- > I looked at scanreg /restore ... > .... but it takes me back a few years Years? You should have had 5 'fairly recent' rb00x.cab filles offered, at least one of which (hopefully) pre-dating your printer installation. Take a look in the \windows\sysbckup folder to confirm. But remember, these 5 files update each (power-up) day (FIFO) so the longer you leave it, the less chance you'll have of getting a potentially 'good' registry (and attendant files) back again. You could also take a look at win.ini or system.ini with a text reader (e.g. notepad) and see if there are any references to your printer which might be causing the error report. If there is an orphaned line in one of the files, scanreg /restore 'should' resolve it - subject to the constraints mentioned above. There *may* even be a win.old or system.old file floating about that 'just' predates the printer installation which you could salvage. But from this distance, I'm running out of ideas. Good (Irish) luck Mart >>BTW - Sorry if a daft question, but... You did remember to physically >>disconnect the printer before trying to troubleshoot ? [quoted text clipped - 24 lines] > set a > restore point before I tried to add theprinter. Lesson learned I guess. > I looked at scanreg /restore > (thanks for the suggestion)but it takes me back a few years which > might be when my son crashed it with a virus so I guess I would use > that as a last resort. I might try to restore to the original error > before I tried anything and see what I can do. This suggests that for some reason the scanregw entry is no longer present or at least no longer checked in MSConfig | Startup as otherwise the registry is backed up automatically the first time that the PC is switched on and booted each day. Not important now but something I feel you might want to correct once you have solved your other problems. SignatureMike Maltby MS-MVP Windows [2001-2006] mike.maltby@gmail.com . > Yes I disconnected the USB cable. I looked at scanreg /restore > (thanks for the suggestion)but it takes me back a few years which [quoted text clipped - 8 lines] > remembered to set a restore point before I tried to add theprinter. > Lesson learned I guess. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.