This one is an odd one. I have been a regular user since 3.10 so I have done nothing "unusual" in my preparations.
I downloaded the latest 3.13 and ran it on a WinXP with the latest SP3 build.
The result did not see any hard drives on my machine. 3.11 did, since although my machine requires a special SATA drivers, the BTS driverpack data is included in UBCD and it worked fine.
So I tried it on an older Pentium 4 that has no special SATA requirements... still didn't see drives (regular 30Gb IDE). So I tried it on a Pentium III (18Gb), same result... no drives. I have a dual processor Pentium II 350 (40Gb) that I tried to be SURE, and still no joy. (There's one for the 'old computer' thread!)
Here are the combos I tried:
XP non-final SP3 and UBCD 3.13: no drives on P4, PIII, dual PII
XP SP2 and UBCD 3.13: no drives on P4, PIII, dual PII
XP non-final SP3 and UBCD 3.12: works
XP SP2 and UBCD 3.12 using plugin directory from 3.13: no drives on P4, PIII, dual PII
So, with that last one, I figure unless my thinking is wrong, some plugin from 3.13 is causing the problem. Driverpacks:storage enabled, and no third-party plugins FWIW.
Anyone else run into something like this?
Edit: I want to make it clear that in the above circumstances, I did not use any special programs in the preparation of XP, I slipstream manually at the command line and did not remove any components.
Full Version: Cannot see drives!
The only currently supported version of XP are SP1 and SP2 .... SP3 support will only come later some time after its actual release.
Also, do not use anything but a regular source. By adding other updates / hotfix's or by altering the source will result in odd behaviour. So don't use n lite or other methods to alter the source files... they must be an unaltered source.
Also, do not use anything but a regular source. By adding other updates / hotfix's or by altering the source will result in odd behaviour. So don't use n lite or other methods to alter the source files... they must be an unaltered source.
The only currently supported version of XP are SP1 and SP2 .... SP3 support will only come later some time after its actual release.
XP SP2 and UBCD 3.13: no drives on P4, PIII, dual PII
XP SP2 and UBCD 3.12 using plugin directory from 3.13: no drives on P4, PIII, dual PII
Also, do not use anything but a regular source. By adding other updates / hotfix's or by altering the source will result in odd behaviour. So don't use n lite or other methods to alter the source files... they must be an unaltered source.
I did not use any special programs in the preparation of XP, I slipstream manually.
Anyone got any ideas?
XP SP2 and UBCD 3.13: no drives on P4, PIII, dual PII
XP SP2 and UBCD 3.12 using plugin directory from 3.13: no drives on P4, PIII, dual PII
Also, do not use anything but a regular source. By adding other updates / hotfix's or by altering the source will result in odd behaviour. So don't use n lite or other methods to alter the source files... they must be an unaltered source.
I did not use any special programs in the preparation of XP, I slipstream manually.
Anyone got any ideas?
QUOTE
Anyone got any ideas?
I would say you need to try again from a source you know has not been changed and make sure nothing like winodws defender is running while you are slipstreaming because the errors you are having are normally related to the slipstream process or extra updates integrated into the source files.Your 1st post says you are using n l i t e , and you had another "Unrelated" issue you were about to post, which is this topic, so we certainly have to ask these questions.
It's easy to mix up source files when you are trying several different versions with pebuilder, I know this because we have to test against all known working sources for each release to make sure nothing gets broken in the update process. Try doing it from scratch, from the command line, and you may be best off in safe mode so you know nothing is messing with the slipstream process.
I had a really bad "Battle" the last time I had to update my XP setup CD because of "Windows Defender" running in the background in Vista64 after I had disabled it.
For some reason, one of the updates MS pushed down had re-enabled the program and it was changing the ASH HASH of the driver files and windows would not install without a nice fat BSOD.
In part I did base my response from your other post here http://www.ubcd4win.com/forum/index.php?s=&...ost&p=59138 where... and I quote...
Now you are saying...
I currently don't know which story to believe then...
Note this part "*restricted project name, please email Ben for support*" refers to n lite itself... something now I guess you are denying?
QUOTE (FDV @ Apr 15 2008, 12:22 PM) 
I just used *restricted project name, please email Ben for support* last night and ran UBCD4Win on the result. I got lots of errors of course, but I cut them down one by one in the source of the UBCD files. After about an hour, I still got errors but was at a comfortable place so I made an ISO manually (thankfully the software completes the build process despite errors, even if it doesn't ask if I would like to proceed making an ISO anyway).
In any case, I saved a lot of space, about 100mb, so it's worth a shot if you're patient. I didn't keep the build as it had an unrelated problem which I am about to post.
In any case, I saved a lot of space, about 100mb, so it's worth a shot if you're patient. I didn't keep the build as it had an unrelated problem which I am about to post.
Now you are saying...
QUOTE
I did not use any special programs in the preparation of XP, I slipstream manually.
I currently don't know which story to believe then...
Note this part "*restricted project name, please email Ben for support*" refers to n lite itself... something now I guess you are denying?
@rdsok
No need to be obnoxious!!
Just because someone has two conflicting post, does not mean that they are not in fact trying more then one source for the project files.
It's more likely that they may have mixed them up and don't know that the folder they are using has been corrupted and is worthless for use with any PE Build.
No need to be obnoxious!!
Just because someone has two conflicting post, does not mean that they are not in fact trying more then one source for the project files.
It's more likely that they may have mixed them up and don't know that the folder they are using has been corrupted and is worthless for use with any PE Build.
trying more then one source for the project files.
Exactly so. I think I'm going to go with corrupted UBCD4WIN directory on this one... I keep SP2, SP3, and n-- in separate folders, and can get things working with an old plugins folder, so I think I must have tweaked some plugin in my 3.13 download to cause this.
Exactly so. I think I'm going to go with corrupted UBCD4WIN directory on this one... I keep SP2, SP3, and n-- in separate folders, and can get things working with an old plugins folder, so I think I must have tweaked some plugin in my 3.13 download to cause this.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.