My first thought is that you don't have the CD in the Z drive ... You should get the same error from the All In One option as well.
what do you think ?
Login to Account Create an Account
Posted 27 December 2003 - 06:38 PM
Posted 27 December 2003 - 07:06 PM
Posted 27 December 2003 - 08:03 PM
Posted 27 December 2003 - 11:17 PM
Posted 28 December 2003 - 02:18 AM
Posted 28 December 2003 - 02:22 AM
-- 19:22:16 --> Try to find Source CD.
-- 19:22:16 --> Look for CD-ROM Drives.
Error: Cannot Verify XP Source. Tried Home and Pro.
Press any key to continue . . .
I used AiO and it didnt have this error.
Posted 28 December 2003 - 06:01 AM
Posted 28 December 2003 - 08:09 AM
Please let me know these answers, so I can look further. Also, NETHFCHK is much more complete than QFECHECK.
Posted 28 December 2003 - 08:20 AM
EDIT: I found all on the web. Lazy me
I will be back when get those and do some ghosting on PC so wont have reinstall whole lot again.
Have a very happy New Year...
Posted 28 December 2003 - 08:37 AM
Just saw your edit ... I hope we get this BEFORE the New Year! Ghosting is a very good idea ...
File removed for bandwidth considerations ...
Posted 28 December 2003 - 09:26 AM
Posted 28 December 2003 - 09:53 AM
1. Download the attached (work in progress) XPCREATE.CMD file, as well as the XPCREATE.ZIP distrubution. Extract the zip to an empty directory, and overwrite XPCREATE.CMD with the attachment.
2. Run the updated XPCREATE.CMD, and select the M option, then the W option (to add you serial number). Then select the N option (don't forget to put the CD in the drive). This should create a new ISO from the original CD without any source modification, and the addition of WINNT.SIF. This option should create the ISO in under 10 minutes.
3. Test without further modification. you will need to do the F6 thing if your main disk is on RAID. Not that familiar with the different RAID/SATA scenarios: Is it on the MD, can it be set as a standard IDE (for this test)? In any event, the objective is to assure that we can get something going, and this should be quick.
As you said ASAP, I'll post this, and then work on the 2nd setup. I know this may seem like a waste of time, as the output is simple, and not complete as we'd like, but who knows: there may be something as silly as a hardware conflict that will never work. Let me know what you think, and if you still have a Internet connection while running your setup.
Posted 28 December 2003 - 10:16 AM
Nah I dont have a virtual PC so what I do is Ghost whole system and later after if installation fails I will restore whole lot. On my machine it takes about 15 min to restore whole lot.
Posted 28 December 2003 - 10:40 AM
Steps two and five could concievably be skipped. The difference in "Cabs" and "No Cabs" options should not effect the running or installation of XP, but it does insure file integrity of the CD (probably of minor importance in a home user environment), and NO CABS is substancially faster.
Using the same directory and set of files from the first step, and your original XP CD WITH SP1 already slipstreamed (for time saving ... ) add the hotfixes into the HFTYPEn directories. You can reffer to THIS page to see what goes where. From XPCREATE, select the P option to edit the INI file, and change "SLIPFLAG=11" to "SLIPFLAG=00". Save the file, and select the N option from XPCREATE. This will create a CD where the service pack has been slipstreamed, and the hotfixes applied (NOT slipstreamed).
Same as Second Step, only change "SLIPFLAG=00" to "SLIPFLAG=11" before selecting the N option. This will create a CD where the service pack has been slipstreamed, and the hotfixes slipstreamed (NOT applied).
Add your RAID drivers to the CDROOT\$OEM$ directory AND the FILESCD\$OEM$ directory, and update your WINNT.SIF file with the DriversPath info in both the FILESXP and CDROOT\I386 directories, and select the I option. This will quickly create an ISO image from the previously prepared CDROOT with the drivers ready to go.
Create a last CD with the F option. This will take longer, and will update and merge the DRIVER.CAB files, where the XP drivers are stored.
If the error happens after the first step, I'm afraid it is beyond my ability to debug remotely. The CD created here is about as basic as it can be. If the error happens after the second step, it will still be difficult ... If the error happens after the third step, then it is one of the hotfixes that is causing the problem. If the error happens after the fourth step, it is your RAID drivers slipstreaming that is causing the problem. If it happens after the fifth step, it is my handling of the DRIVER/SPn .CAB files.
A question: you may have said earlier ... how to you integrate the RAID drivers? Do you just add the line to WINNT.SIF, and the files, or do you edit TXTSETUP.SIF? Do you do anything "fancy"?
I'm off for about three hours. Please post any findings of interest, and good luck. I owe you a few blank CDs ...
Posted 28 December 2003 - 11:38 AM
Followed your directions.
Extracted SVCPACK.INF from the cab after renaming SVCPACK.IN_...
Extracted. This is what it contains.
Also in i386 was another SVCPACK.INF (Probably due to Slipstreaming WMP9 and DX9)
update.exe -q -n
Notice the reference to Update in the one located in i386?
I relocated the files inside of it to SVCPACK and deleted the folder named Update.
Now, my understanding is the INF should actually NOT be directly in the i386 folder, but should be SVCPACK.IN_ for Windows to properly see it. So I copied from
and moved it into the one I extracted. That updates that one. Now I just need to figure out why the compressed one was not updated with the necessary locations to the Hotfixes.
update.exe -q -n
I am always willing to manually edit the file, and then add it back to the ISO.
And yes, I use Virtual PC. Absolutely LOVE it. Saves time and hassle. Error pops up during Install, and I can shut down the VPC and find out what caused it.
Please lemme know.
PS Oh yeah. the SVCPACK folder is there, and has a BUNCH of files in it. Both CAT and EXE
Posted 28 December 2003 - 02:23 PM
Posted 28 December 2003 - 02:30 PM
Very strange ... The first SVCPACK.INF is from the slipstream of WMP and DirectX. I'm curious as to how you slipstreamed this, and who/what created this file. Are the .CAT files listed in the SVCPACK directory?
The second SVCPACK.INF is from a slipstream of the rollup.
XPCREATE's SVCPACK.INF is no where in sight ... You should see the real SVCPACK.INF file in the NEWFILES directory where you ran XPCREATE.
You are apparently doing, or have done, all three of these manipulations. Unless you have a special need to slipstream DX and WMP, you only need XPCREATE, which will install (without slipstreaming) these items, as well as slipstream the rollup (which you must have done by hand ... ).
In short, run XPCREATE with an original XP CD in the CD drive, and the desired files in the corresponding directories (hotfixes, updates and service packs), and you should not see any of these problems.
How did you slipstream WMP and DX?
EDIT:: You should not have both SVCPACK.INF and SVCPACK.IN_. Only one will be used, but I can never remember which one... XPCREATE replaces the compressed version with a new, compressed version.
@czaja74: I'll be on hold, waiting for your report ...
Posted 28 December 2003 - 03:28 PM
As about my way to do SATA/RAID drivers (same will apply for PATA RAID) please look at the link I have provided earlier. It will not be really hard to implement it. There are only few controllers. Silicon Image, High Point, Promise and this will be it. All you might need is IF or Switch statement and assotiate actions. Basically have a menu to install RAID drovers and submenus for different controllers. All will be needed is to copy driver files (that easy part) and add few lines in the paticular locations in the TXTSETUP.SIF and put the path to the winnt.sif file. Also put .sys file in the 386 folder. I'm not sure how would you do the part with adding the lines in the TXTSETUP.SIF as they need to be under specified locations [...........]. But this for a future.
PS I have noticed the dos window flashing after last planned reboot saying it cant...... but it was really flash and I didnt read it or maybe read wrong. Will it be in the system logs?
Posted 28 December 2003 - 03:41 PM
- The performance Counter namestring value in the registryis incoretlly formated. The Bgus string is 2272 the bogus index value is second and third DWERD in DATA section.
-Unloading the performance counter strings for serviceWmiApRpl (WmiApRpl) failed. THe error code is the first DWORD in Data section
Some errors in the System logs but these not related.
Posted 28 December 2003 - 03:49 PM
I know what went wrong now.
XPCreate did not create the SVCPACK.INF in the i386 folder, nor the compressed version of it. I suspect that may be because of the Unattended source.
BUT, I did find the new SVCPACK.INF located in Newfiles.
As for slipstreaming DX9 and WMP, I only did that after the 2nd try with XPCreate. I installed the OS in VPC, and it did not register DX as 9 or WMP as 9, but as the 8.1 and 8 respectively. This was due to the SVCPACK.INF not being created. I did not notice this until just a moment ago. That was why I slipstreamed DX9 and WMP9. This was done using the method defined here http://www.MSFN.org/...rectX 9,and,WMP
And I suspect it was the batch files they created that caused it.
I have moved the new SVCPACK.INF from the Newfiles directory into the i386 directory, and am about to install in VPC...
The other thing is, after running XPCreate, I now have a folder named Update in my i386 (NOT on the Unattended Source CD) and the SVCPACK.INF that is in i386 looks like this
update.exe -q -n
Now sure where this is coming from, but again, it is NOT on the source CD and it is NOT in the CDRoot folder when I read from the source CD (I deleted the files located in CDRoot before pulling from the source again)
As I said, once I get the SVCPACK.INF from the Newfiles into the i386, and test it I will let you know how it goes.
As far as I am concerned, if it works and functions, I will be a happy man and will refine it from there...
Posted 28 December 2003 - 04:15 PM
And few updates from recomended ones. Does it mean that sometihng wasn't slipstreamed? Or maybe these werent included.
Posted 28 December 2003 - 04:21 PM
Posted 28 December 2003 - 04:27 PM
I looked over the link in the begining, and yes, I think it will be included ... after I get these bugs worked out. I wanted to look over the site again, and it is "down" at the moment. I hope it comes back: that was a good article.
The flashing window is not a problem. It cleans up a few files, and some are not there. It will not be in the logs, and is not a worry.
There may be something with TXTSETUP.SIF. I change it when you don't select the "No Cabs" option. I cannot get to that article, but do you edit TXTSETUP.SIF before you run XPCREATE? It would be best to edit after XPCREATE, in the CDROOT\I386 directory. What else do you edit: WINNT.SIF, DOSNET.INF?
When you say VP, you mean Virtual PC, right? I know it was my suggestion ... but to test the RAID controller we will need to go "live"
... that was in response to your post about three posts back ... I'm checking out the others now.
Just saw your post, stinkywea. Thanks for the boost! (Let it be known that stinkywea was not paid for his comments ... ) Out of curiousity, did you use the All In One, super dooper, AutoUpdate option?
Posted 28 December 2003 - 04:45 PM
That update directory, and SVCPACK.INF (notice it is not SVCPACK.IN_) are most certainly not XPCREATE's doing ... I'm copying it from somewhere. If it is not on the CD, did you previously use the X option to copy the source to HDD? You really need to start with a "virgin" XP CD. Do a search on your HDD for SVCPACK.INF, and you find the guilty party. It will either be in the CDSOURCE directory, or the directory indicated in XPCREATE.INI, under CDSOURCE=.
The DX9 and WMP9 slipstream by jdeboeck is indeed a good example. I have not had time to test and integrate it into XPCREATE yet, and it may introduce some conflicts at the moment. If XPCREATE works properly, both DX and WMP will be up to date after setup, just not slipstreamed into the source.
Let me know how it goes in a "clean" environment.
Posted 28 December 2003 - 04:54 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users