CD-ROM Dissappeared! - Page 2
Page 2 of 2 FirstFirst 1 2
Results 16 to 29 of 29

Thread: CD-ROM Dissappeared!

  1. #16
    Registered User
    Join Date
    Apr 1999
    Location
    Washington, USA
    Posts
    47

    Unhappy

    Installing Windows over Windows? ... wouldn't that cause a problem somewhere? Especially with an established registery, etc.?


  2. #17
    Registered User
    Join Date
    Oct 1999
    Location
    Clackamas, OR USA
    Posts
    5,422

    Post

    Best way to reinstall Windows over Windows without damaging or losing settings in the registry yet getting the cleanest possible install as well is to rename the win.com file in the Windows directory, reboot to a DOS prompt and run the setup.exe on your install CD or better yet, copy the WIN9x directory from the CD to the HD and run the setup from there. One important note: when it asks for the install directory it will default to C:\windows.000. Simply choose other directory then remove the '.000' from the path and you're off, just like a clean install without losing all your settings.
    "Badges? We don't need no stinking badges."

  3. #18
    Registered User techs's Avatar
    Join Date
    Aug 2000
    Location
    In one of the really, really Blue states.
    Posts
    5,159

    Post

    i my not be the most experienced tech here, but before i would reinstall windows i would boot to win98 floppy with cd rom support and see if it finds the cdrom. have you considered the cdrom has gone bas.

  4. #19
    shanff
    Guest

    Post

    just install tweakui and go to the drives tab? anyway, uncheck the "hidden" drives there, too many people like to hide drive letters and it makes for this kind of problem when drive letters change.

  5. #20
    Logan
    Guest

    Smile

    I agree with Techs I would try a different cdrom first to rule out that it is a bad cdrom.

  6. #21
    Registered User
    Join Date
    Apr 1999
    Location
    Washington, USA
    Posts
    47

    Red face

    It is not a bad cd-rom.

    All scenario's have panned out empty. Its a ghost in the machine.

    Weird.

    Thanks though.

  7. #22
    Registered User
    Join Date
    Oct 1999
    Location
    Clackamas, OR USA
    Posts
    5,422

    Post

    The one thing I don't see is a mention of the CD driver being loaded in config.sys. A '.sys' file for the CD in config.sys will usually keep the CD from appearing in device manager yet still enable the drive to work in a DOS window.

  8. #23
    Registered User
    Join Date
    Aug 2000
    Location
    San Antonio TX
    Posts
    264

    Post

    You might want to update your bios and controller drivers. Seems that the driver that windex is trying to load for the cdrom is not compatible. what brand is the cdrom anyway.

    ------------------
    hey its me again!

  9. #24
    Registered User
    Join Date
    Apr 1999
    Location
    Washington, USA
    Posts
    47

    Talking

    The CD-ROM works perfectly well, in a DOS mode/window. The device is listed as A-OK in device manager.

    Current drivers are present and accounted for. The drive is a base mitsumi 24x.

    I don't want to sound like a tech. show freak, but I have done all the things that field experience and schooling has given me - and all of your great suggestions.

    This thing is just gone.



    ------------------

  10. #25
    Registered User techs's Avatar
    Join Date
    Aug 2000
    Location
    In one of the really, really Blue states.
    Posts
    5,159

    Wink

    after being a tech for two years i have found out that sometimes the answer is "I don't know".

  11. #26
    MegaMod DonJ's Avatar
    Join Date
    Aug 2000
    Location
    San Antonio, Texas
    Posts
    2,692

    Post

    Hi,
    I know you said you messed with the autoexec.bat file in c:\ directory...not c:\windows. Verify that you have the following: "MSCDEX /D:MSCD001 /L:M"
    --where /D: is the device driver and /L: is the letter of the CD-ROM drive. It is usually set to "D" but HP's Pavilions usually set them to "M."
    Also, do as NightVa said...make sure that config.sys has "LASTDRIVE=Z".
    Save changes and reboot...go to Control Panel and the CD-ROM should reappear.
    Hope I'm not rehashing old info...I know that I had the same problem tho.
    Good Luck!
    DonJ
    I'm good enough.
    I'm smart enough.
    And doggone it,
    People like me!

  12. #27
    GIG-O-Tech
    Guest

    Post

    Ok... I've had a similar problem once... something to do with a bad plug and play chip in the cd-rom itself (I'm guessing) have you tried a new cd-rom? It may just be that simple... but if not.. here's another suggestion.

    Boot into Safe Mode (by pressing F8 when it say's Starting Windows 9x) and goto the device manager and remove all instances of duplicated items.. i.e. if there are more than one cd-rom listed in there delete both of them.. and you may want to delete the cd-rom out of there regardless this has cured many problems I've had with other hardware.

    is there anything you've changed prior to running into this problem? even something small.

    well I hope this helps.. seems you've got a lot of really good suggestions already... but I honestly feel that the drive has just had it...

    best of luck

    Jeremy

  13. #28
    shawnMt
    Guest

    Post

    1. Make sure the cab files are on your hdd
    2. Boot to Safe Mode (very important)
    3. Go into Device Manager
    4. Remove all cdroms
    5. Remove all the IDE controller stuff that Windows will allow you to remove
    6. Reboot normal and let Win find what is there

    Try the above first but if all else fails delete the "Enum" key from hkey_local_machine before you resort to wiping the drive and reinstalling...
    ------------------
    Computer Geek + Football Freak - man I have issues

    Paint your old laptop!

    [This message has been edited by shawnMt (edited September 09, 2000).]

  14. #29
    norcalbmxer
    Guest

    Angry

    Guys- He has said that it works if he drops to dos. My conclusion from this is the CD WORKS....Also that config.sys / autoexec are good.... that would mean that something on the 32-bit side is hosing this thing. The only time i have had problems like this are either when the novell client is over mapping drives via login scripts, or if the users local and or network stored profiles are hosed....ie just deltree c:\windows\profiles\%USERNAME%....and the one stored on the network end to.....but since i think this system is yours at home, i doubt either of these fixes will apply to you....so my fix in that case would be
    format c: /q

    haha Have Fun...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •