It kept saying that I needed to insert a blank CD and click Next, which I did, the but Next button didn't seem to have any effect. I then had the problem that Boot Media Builder refused to write to my CD-drive.
PARAGON WINPE RECOVERY MEDIA BUILDER INSTALL
I was concerned it might be infected, so before attempting a build of a boot media CD there I restored back to the factory settings, reinstalled the update to Windows XP, applied a zillion patches, installed Windows AIK (which required an install of MSMXL, and Virtual CloneDrive read the downloaded image), and finally the Boot Media Builder. My old system is definitely 32-bit (circa 2000). My guess is the problem is a driver problem but that's what it is, a guess.Ĭlick to expand.No, I meant that the after dismissing the network message, the program started successfully on that system. It could be that the problem is the same as the typical Linux problem where the default driver complement is not well suited to the hardware and the proper driver needs to be loaded into WinPE. Unfortunately I do not know how Paragon incorporates the drivers into its WinPE disk when it is built or in other words is it more machine specific because it analyzes the hardware than the machine independent Linux that comes with the free version. A 64 bit version of the OS requires the 64 bit version of the drivers and the 32 bit drivers for the 32 OS.Īnother problem is that 64 bit drivers are not available for all hardware especially older hardware and IMO there are a lot of buggy 64 bit drivers out there but with the wider adoption of 64 bit Windows the situation is getting a lot better now but you still read about various programs that croak under 64 bit Windows and are OK with 32 bit. Where the problem usually lies is in the drivers. Most likely the WinPR disk won't boot up because it detects the wrong bit-size OS and knows it would make things worse. Most PCs purchased for the past few years are 64 bit machines in terms of the hardware and can run either 32 or 64 bit OS. I don't think the issue is 32 vs 64 bit hardware.
0 kommentar(er)
