Jump to content

jostrus

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by jostrus

  1. This sounds like its a problem with the disc / drive combination. Possibly the speed at which it was written? Try a slower speed or another brand of media? I've never had this problem that you are encountering. So I'm not sure what to try next.
  2. Just to save some people some time. In winpe2 "Classes\CLSID\{43A8F463-4222-11d2-B641-006097DF5BD4}\InProcServer32","","%SystemRoot%\System32\shdocvw.dll" is ieframe.dll. The shdocvw.dll is not included by default but you could take it from a vista machine however that does not make it display the correct dialog. All the other registry keys are there. I ran a dependency check and copied all the files from a vista ultimate machine into the pe image and it still did not work. I'm sure there are other class registries missing, just for kicks I exported the entire class hive from the vista machine then used a text editor to search/replace the c: with x: then put a reg file in the pe image and tried loading it with all the new files copied for dependency check and it still didn't work. This isn't really my cup of tea so I'm not too sure where to go from here but I hope that helps someone else maybe figure it out. BTW even on the real vista machine the key above is ieframe.dll. I tried using a shell32.dll from xp and changing around some other registry keys but I kept getting shlwapi errors so I called it quits since its really late.
  3. If you mean how do you get rid of the "Press any key..." message during the boot rename/delete the bootfix.bin file.
  4. Are you burning with Nero directly or from UltraISO using the Nero API? Are you getting any errors with Nero when burning? Which version of UltraISO? On a personal note I've been having problems trying to burn using UltraISO when it uses the Nero 7 API it keeps failing at random parts of the burn process. The workaround I use is just rename a file in the layout and then back so its a *modified* file and it'll use the Windows on the fly burning engine which isn't really that great but for now it's the only successful method I can use on that one computer. Something you could try is make an MD5 checksum of the files in the ISO before you burn, to do so load UltraISO with the iso file, click File | Create Checksums; and save to file of your choice. After you burn with whichever method you try have UltraISO compare the MD5 to the CD copy to make sure the files are correct and that your problem isn't the computer you're using the burned disc in. To do so insert the disc into DVD drive of choice, in UltraISO click Tools | Verify CD/DVD Checksums. Select the drive the disc is in and the MD5 file you created before. Click verify. It will probably take a while and scroll a lot of stuff through the screen when its done you can use the filter drop down to select to show any files that failed so you can get a quick glimpse of what's going on. Another thing you might try if you still have the original disc is use UltraISO to make the ISO directly from the original media and try burning and see if that works. There could be a bug in the conversion from CloneCD to ISO format causing your problems. Sorry if you already did and I misunderstood what you said in your original post. I try to avoid any conversions that are uneccesary.
×
×
  • Create New...