Recommended Posts

Hey,

I've been trying to install windows 7 build 7077 on a HP nc6910p laptop (that had previously been able to install the beta on) and during the install it says there is a cd/dvd driver missing so it can't install?

Is this thing yanking my chain or do I have a bad image? Is it a common problem, as I thought most cd/dvd drives used universal drivers??

cheers

Same issue here when attempting to install build 7077 onto my aging desktop.

At this stage I haven't been able to resolve to it as I am unsure what drivers it is after exactly.

I am currently running the public beta (build 7000) which did a clean install without an issue.

I was attempted a clean install of 7077 when I encountered the message. I believe you can upgrade 7000 to 7077 but I would prefer a clean install and am thinking that the upgrade would most likely corrupt my working build.

One thing I have tried is creating a bootable usb flash drive with the install on it. Unfortunately my motherboard does not support USB boot so this didn't work either.

I am keen to hear if anyone else out in the community is having similar issues and if there are any workarounds other than waiting for the next build (or hopefully RC)

Thanks

Download the latest drivers for your chipset, put them on a flash drive or floppy disk (if you still have one in your pc, :laugh: hehehehe) and when that "cd/dvd driver missing" pops up, specify the place where you have the files! I stumbled upon the same issue with build 7057 and had to copy the drivers from another build or the infinst_autol package so i could install win7. It worked.

If you'd rather having the win 7 build 7077 files instead of the files coming from intel's package, search for these files on an older build win 7 iso/dvd. Mount install.wim if needed:

aliide.sys

amdide.sys

atapi.sys

ataport.sys

drvbck.pdb

intelide.sys

msahci.sys

mshdc.inf

pciide.sys

pciidex.sys

Storprop.dll

viaide.sys

They usually reside in windows\system32\driversstore or something.

If you like intel's version, download this!

http://downloadmirror.intel.com/16023/a08/infinst_autol.exe

Greets

Edited by kukubau
  TTSoarer86 said:
Thanks for the tip kukubau,

I will give it a go tonight.

The driver may be removed as an oversight, temporarily for some other reason, or deemed unsuitable at the time. We don?t know. This is why unofficial builds are not normally released.

Post back if it worked!

kukubau

I tried pointing the windows installer at both the system32\drivers and system32\driversstore of my successfull build 7000 install but it wouldn't accept either. I also tried the Intel drivers that you provided the link to but I don't think my motherboard supports them. I was unable to find drivers for the ASUS P4S8X motherboard which i believe has the Sis 648 chipset onboard.

Am interested to hear which motherboard and chipset combinations ADDeveloper and Si_ are running.

Thanks for the help but I think I'll await for the next release to be leaked

Try these! The files I mentioned from build 7057.

I hope it works this time.

Rename chipset.txt to chipset.rar. For some reason I am not allowed to upload *.rar files.

Unpack the archive to your flash drive and see if it works now. I bet you a Guiness it will.

edit: chipset.rar

chipset.txtFetching info...

My main system is running on an Asus P5N32-E Motherboard which has the nForce 680i SLI SPP Chipset. Does that mean I need the nForce drivers? They come in a package so how do I get the windows install to recognize them?

Interestingly I purchased a dell Inspiron and tried to install Win 7 build 7077 on it. That failed as well with the same error...

The motherboard on that is listed as a Dell Inc. 0G848F with Intel GM45/GM47 chipset and Intel 82801M(ICH9-M) Southbridge.

I tried kukabau's chipset.rar drivers but that didnt help either.

Bah's. Bah's I says! Whats the build closest to 7077 that may work? I am currently running 7068.

Edited by ADDeveloper
  Si_ said:
Hey,

I've been trying to install windows 7 build 7077 on a HP nc6910p laptop (that had previously been able to install the beta on) and during the install it says there is a cd/dvd driver missing so it can't install?

Is this thing yanking my chain or do I have a bad image? Is it a common problem, as I thought most cd/dvd drives used universal drivers??

cheers

Had the same problem, but was able to work around it by running it through a usb dvd drive. If you don't have usb capabilities then down load drivers for the dvd drive you are using (if it didn't come with a drivers disk). For my son's computer (no usb capabilities) I ran it from the present OS (because of the same problem), and was able to load it that way (just took longer).

Hope this helps

What's weird is that error shows up for different scenarios. For me, the ICH5 chipset drivers were removed from build 7057, for you guys it seems the cd/dvd om drivers are missing.

Install a previous working win7 build and use software for backing up drivers like Driver Magician or Uniblue Driver Scanner. Driver Magician helped me back up all the Windows and non windows drivers that I though I might need another time.

Last try. I uploaded the cd-rom drivers from build 7057, but I doubt that will work for you guys. Try and see. It might.

Rename CD-ROM Drive.txt to CD-ROM Drive.rar!

@ADDeveloper

Try the Intel package(link posted before), that's an Intel mobo.

Greets.

CD_ROM_Drive.txtFetching info...

kukubau, I almost thought that I was going to owe you a Guiness!

I tried each of the chipset drivers but none of them were accepted. It though long and hard about accepting the cdrom one then came up with the same message.

I managed to get a couple of photos, the first showing the original message requesting the cd/dvd driver and the other the rejection message.

Is this the same message that you are getting ADDeveloper?

I may look into Driver Magician as I am still currently using build 7000.

If I have any success I will be sure to let you know.

post-288308-1239879003_thumb.jpg

post-288308-1239879033.jpg

Just about ready to give up.

Used Driver Magician to backup all of my current working drivers from 7000.

The message is rather vague so I tried selecting anything to do with CD Drives, IDE Channels, or motherboard chipsets but of all the drivers I tried none were accepted.

I am hesitant to screw up a working version of 7000 but am considering attempting an upgrade rather than a clean install.

@TTSoarer86

What SIS IDE Controller do you have on your motherboard? I'm interested in the part number. Use Driver Magician to backup the driver for it and try to install 7077.

If what you're saying is true it might have to do with other components in your system.

I remember now that I had to unplug the harddisks from my SATA Raid Silicon Image controller to make it work. You might have a raid array defined.

Unplug those disks and leave only the one you're installing win7 on.

  ADDeveloper said:
My main system is running on an Asus P5N32-E Motherboard which has the nForce 680i SLI SPP Chipset. Does that mean I need the nForce drivers? They come in a package so how do I get the windows install to recognize them?

Interestingly I purchased a dell Inspiron and tried to install Win 7 build 7077 on it. That failed as well with the same error...

The motherboard on that is listed as a Dell Inc. 0G848F with Intel GM45/GM47 chipset and Intel 82801M(ICH9-M) Southbridge.

I tried kukabau's chipset.rar drivers but that didnt help either.

Bah's. Bah's I says! Whats the build closest to 7077 that may work? I am currently running 7068.

You might want to unpack the nforce drivers on a flash drive.

Export all the drivers from b 7068 with driver magician and try again!

Edited by kukubau
  • 2 weeks later...

Have same issue with the 64bit of the RC. What a headache. No solutions yet?

apparently there must be a problem with a combination of Sata and IDE style drives. I can not be sure of this but I would definatly keep this in mind if other people are having similar issues.

Edited by BoDEAN
  • 2 weeks later...
  BoDEAN said:
Have same issue with the 64bit of the RC. What a headache. No solutions yet?

apparently there must be a problem with a combination of Sata and IDE style drives. I can not be sure of this but I would definatly keep this in mind if other people are having similar issues.

I was getting the same error in VirtualBox and loading it directly on my PC. So, at the suggestion of someone on one of the other boards, I re-burned the .iso image at a slower rate (8x) and that worked. I was able to install it with no problems.

Nex

  TTSoarer86 said:
kukubau, I almost thought that I was going to owe you a Guiness!

I tried each of the chipset drivers but none of them were accepted. It though long and hard about accepting the cdrom one then came up with the same message.

I managed to get a couple of photos, the first showing the original message requesting the cd/dvd driver and the other the rejection message.

Is this the same message that you are getting ADDeveloper?

I may look into Driver Magician as I am still currently using build 7000.

If I have any success I will be sure to let you know.

pls help me. i am unable to install win 7 because while i click/through dvd setup its show autorun.dll error.i have three months activation key but i am unable setup.is anyway to solve this problem?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • KDE's KClock is getting Wayland Picture-In-Picture support by David Uzondu The KClock app for KDE Plasma over the years has received a number of updates, like better integration with KRunner and a dedicated background service (kclockd) for managing alarms. Now, it looks like KDE devs want to add something cool: pop-out timers using the new Picture-in-Picture protocol for Wayland. Image: Kai Uwe Broulik This all started from a simple observation. Kai Uwe Broulik, a KDE developer, saw someone using a small timer window during a presentation and thought it was a good idea. The problem is that achieving this kind of "always on top" behavior is handled differently between the old X11 display server and the newer Wayland. With X11, an application could pretty much do whatever it wanted. If a program wanted to draw a drop-down menu, it would just create a borderless window, place it in a specific spot, and grab all user input. Wayland operates on a different philosophy. As Broulik notes, under Wayland, the application describes what it wants, and the compositor gets to decide how to handle it. A drop-down menu is an XDG Popup. The application tells the compositor which button spawned it, and the compositor handles the placement and behavior. This is much more secure and consistent. It also means an application cannot just decide to keep its window on top of everything else. This restriction prevents a web browser from implementing an overlay video player under Wayland. To get around this in a standardized way, a proper Wayland support model for Picture-in-Picture, or PiP, was needed. Enter the xx-pip-v1 protocol. It is a new protocol designed specifically for creating floating PiP windows, and KWin, Plasma's compositor, recently gained support for it. Because it is an experimental protocol, its use is gated behind an environment variable, KWIN_WAYLAND_SUPPORT_XX_PIP_V1. A new protocol is fine for demos, but it needs a real application to find its weaknesses. So Broulik implemented it in KClock. This work allows KClock to offer pop-out timers and even a pop-out stopwatch in a small PiP window. The user could get system-wide options to control where the PiP window appears, or if it appears at all, and have that setting apply to every single application that uses the protocol. You can check out the merge request on GitLab for more technical details about this feature.
    • Nothing of course; it is just a classic syndrome of MAGA pathology.
    • They use it to assessment's in the UK already. Have a friend who said they basically feed response's and prompt during assessment's for many mental health conditions now (essentially tick boxes these days enough ticks and you got it) the AI can prompt questions to ask if its unsure how to score something. It's really good at recognising fractures and broken bones also.
    • Look it more of another tool in your toolbox. The good doctors will use tools like this to aid in proper diagnostics and help their patients. There will be some doctors out there that will rely on it and never actually learn how to be a doctor. My wife deals with chronic illness, seizures, and MS. If this would help her doctors to get her on a better path to recovery, I'm all for it. She does take about 4-5 different medications daily and no one wants to play Russian roulette to figure out which meds she really needs.
    • I'm currently wearing Hoka Clifton 8.  It's a good shoe.
  • Recent Achievements

    • One Month Later
      CHUNWEI earned a badge
      One Month Later
    • Week One Done
      TIGOSS earned a badge
      Week One Done
    • First Post
      henryj earned a badge
      First Post
    • First Post
      CarolynHelen earned a badge
      First Post
    • Reacting Well
      henryj earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      +FloatingFatMan
      196
    3. 3
      ATLien_0
      163
    4. 4
      Xenon
      81
    5. 5
      Som
      77
  • Tell a friend

    Love Neowin? Tell a friend!