Just do the integration before going to the update checker screen. If you use the same settings all the time, slipstream as early as you want, if you change options, just slipstream from the overview screen.
1 2009-09-16 18:59:00
Re: [IMPL] BASE 8.12.x or better - Freeze on update page if no Internet (7 replies, posted in Feedback and Support - DriverPacks Base)
2 2009-09-10 03:57:17
Re: Dell M70 missing with install, but found w/DP_INSTALL_TOOL.CMD (37 replies, posted in Software)
Try implementing everything except HID pack.... I believe the issues lie within that pack.
3 2009-09-06 02:37:19
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
Try disabling onboard audio in your system bios and see if the endless reboots stop, I have seen this and is normally caused by hardware conflicts, onboard audio has been the culprit I have seen every time so far, but it is not necessarily the only potential cause.
4 2009-08-29 23:43:19
Re: DP Base [all versions] and the XP 'Repair' Option (55 replies, posted in Feedback and Support - DriverPacks Base)
To do what you want, you need multiple sif's, multiple setup bin's and a multi-boot cd.... I have posted on how to do this, and files to do it before..... If needed, I can upload what I use for the multi-boot options with instructions.
5 2008-03-07 07:30:33
Re: Error with Mass Storage Driver (4 replies, posted in DriverPack Mass Storage)
the next thing i would try since you already downloaded the massstorage driverpack again is deleting the QSC folder and see if that fixes it.
6 2008-03-07 07:24:53
Re: Keeping The "Repair" Option In Windows Setup (11 replies, posted in Other)
Overflow, that is not actually correct.....
That line in the beginning makes the repair option work no matter what the user uses, as long as the [unattended] section is not in the winnt.sif file.
The repair.sif file I use for my multiboots has the complete file, less anything in the unattended section.
No matter what you do, if that section is in the winnt.sif file, the repair option will not be presented.
The DEL /F %systemroot%\system32\setupold.exe line is only to prevent the setup called itself issue during a repair.
Oh... I think I just uderstood what you were talking about. If the user selects M2 AND guirunonce, there is no need to set OEMPreinstall and that would be correct.
7 2008-03-06 21:37:47
Re: Keeping The "Repair" Option In Windows Setup (11 replies, posted in Other)
LOL OverFlow.... sorry, I thought I had pointed it out way back when, when i shared my cmd files, and the method for the users that wanted it in the past....
Sorry bout that man.
8 2008-03-06 21:34:26
Re: Keeping The "Repair" Option In Windows Setup (11 replies, posted in Other)
OverFlow wrote:
the rc version of base includes that fix dizzy
The last check I did, the rc puts it at the end of the file, not the beginning. With it at the end, it has been hit and miss as to working, at the beginning it is flawless.
9 2008-03-05 08:26:52
Re: Keeping The "Repair" Option In Windows Setup (11 replies, posted in Other)
To retain the Repair option, simply remove the entire [Unattended] section, that is all that has to be done.
But, for it to work CORRECTLY, the presetup.cmd in I386 on the CD needs to be edited after you run DPBase.....
DEL /F %systemroot%\system32\setupold.exe
that needs to be at the BEGINNING of the cmd file.
10 2008-02-22 07:36:11
Re: [Existing Feature] [REQ] 8.3 naming for DP's (14 replies, posted in Feature Requests)
hmmmmmmmmmmm, guess i'll keep searching why they are not being renamed for me.....
11 2008-02-21 09:44:26
Re: [Existing Feature] [REQ] 8.3 naming for DP's (14 replies, posted in Feature Requests)
Nope, running XP Pro SP2 updated
12 2008-02-21 07:55:53
Re: [Existing Feature] [REQ] 8.3 naming for DP's (14 replies, posted in Feature Requests)
OverFlow wrote:
Which version of base are you useing?
Base does rename to 8.3 internaly and it always has...
perhaps your local copy of base is corrupted
As stated in my post regarding the contents of my OEM folder, I am utilizing RC2.... I will dl it again and test to see if perhaps it is a corrupted dl, but I wouldn't think everything except that portion would function correctly..... but to rule out or further investigate it is worth a shot.
OK, I downloaded 8.1 RC2 again, deleted all files and folders except my Driverpacks folder. Ran RC2 and my OEM folder at my destination folder contains:
ATICCP.ins
bin
DPC801d.7z
DPCP71220.7z
DPGA8012.7z
DPGB8012.7z
DPGC801.7z
DPL8022.7z
DPM8028.7z
DPSA8022nightly.7z
DPSB8023nightly.7z
DPW802_Nightly.7z
It appears to me that the 8.3 naming convention is broken in the release somehow.
13 2008-02-20 21:32:01
Re: [Existing Feature] [REQ] 8.3 naming for DP's (14 replies, posted in Feature Requests)
mr_smartepants wrote:
During integration, DPBase automatically renames the DriverPacks for 8.3 compliance and even places a .txt file in the OEM folder telling you which DriverPacks were renamed and to what.
Besides, 8.3 filenames are only a concern during textmode setup. Once setup is complete and the finisher runs at either GUIrunonce or ROE, long-filename support is enabled anyway.
I understand and agree that when dpsfinisher kicks off, whether guirunonce from winnt.sif or roe from cmdlines.txt, that lfn support is enabled, but it cannot copy files that were not extracted to begin with, and I suspect long filenames in the extracting phase is the culprit. Sometimes i do rename, i do a lot of testing/tweaking, which has come in handy getting some driver packs fixed here.
mr_smartepants wrote:
Anyway, you could have a DP with the filename DP_Graphics_A_wnt5_x86-32_802_nightly_big_hairy_long_file_name_wowthisisreallylong.7z and it'll still get truncated down to DPGA802n.7z during integration by the Base.
If that were the case, there would be no reason for this request.... here is the contents of my OEM folder on my cd following execution of DPBase 8.01 RC2.....
ATICCP.INS
BIN
DPC801D.7Z
DPCP71220.7Z
DPGA8012.7Z
DPGB8012.7Z
DPGC801.7Z
DPL8022.7Z
DPM8028.7Z
DPSA8022NIGHTLY.7Z
DPSB8023NIGHTLY.7Z
DPW802_NIGHTLY.7Z
Those files were NOT forced to 8.3 naming...
14 2008-02-20 07:52:14
Re: [Existing Feature] [REQ] 8.3 naming for DP's (14 replies, posted in Feature Requests)
To alleviate any confusion, everything apears to copy correctly.... APPEARS TO.... but, that is because during initial copying, it is merely extracting *.7z to %SystemDrive%\D.... following reboot, everything appears to install correctly.... following next reboot... when DPSFINISHER begins, you will get cannot move \D\WHATEVER\DRIVER the file does not exist....
Researching, I discovered I have 7z files with very long filenames (did not rename some nightlies, etc....) hence, I suspect the reason for failure is in extracting files with longer than 8.3 during text mode.... figured forcing to 8.3 by DPbase may avoid the issue. This is what made me think of situations where you COULD have (as an example) DPSA81210.7z.... not that it has happened, but could be avoided by having DPBase FORCE 8.3 names.
BTW, I always use M2, slipstream all DP's (no 3rd party, but a lot of testing of nightlies and my own modifications to them) KTD for all slipstreamed DP's, I do set the KTD folder to %SystemRoot%\System32\Drivers (so they will be in with all other drivers, only in their folder structure) and (not that it matters for this particular issue) QSC enabled.
Here is PART of the DPSFinisher log file (all errors correspond to DP's with long filenames in OEM folder)
2008-02-18 13:41:42 : <ERR> Could not apply KTD on "C:\D\CP", since it does not exist!
2008-02-18 13:41:47 : <ERR> Could not apply KTD on "C:\D\G\A\1", since it does not exist!
2008-02-18 13:41:52 : <ERR> Could not apply KTD on "C:\D\G\A\2", since it does not exist!
2008-02-18 13:41:57 : <ERR> Could not apply KTD on "C:\D\G\N\1", since it does not exist!
2008-02-18 13:42:02 : <ERR> Could not apply KTD on "C:\D\G\N\2", since it does not exist!
2008-02-18 13:42:07 : <ERR> Could not apply KTD on "C:\D\G\N\6", since it does not exist!
2008-02-18 13:42:12 : <ERR> Could not apply KTD on "C:\D\G\3", since it does not exist!
2008-02-18 13:42:17 : <ERR> Could not apply KTD on "C:\D\G\A\4", since it does not exist!
2008-02-18 13:42:22 : <ERR> Could not apply KTD on "C:\D\G\A\5", since it does not exist!
2008-02-18 13:42:27 : <ERR> Could not apply KTD on "C:\D\G\AS", since it does not exist!
2008-02-18 13:42:32 : <ERR> Could not apply KTD on "C:\D\G\I", since it does not exist!
2008-02-18 13:42:33 : <ERR> Could not apply KTD on "C:\D\G\N\3", since it does not exist!
2008-02-18 13:42:34 : <ERR> Could not apply KTD on "C:\D\G\N\4", since it does not exist!
2008-02-18 13:42:34 : <ERR> Could not apply KTD on "C:\D\G\N\5", since it does not exist!
2008-02-18 13:42:35 : <ERR> Could not apply KTD on "C:\D\G\M", since it does not exist!
2008-02-18 13:42:36 : <KTD> Moved drivers inside "C:\D\G\S" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD> Moved drivers inside "C:\D\G\S3" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD> Moved drivers inside "C:\D\G\T" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD> Moved drivers inside "C:\D\G\V" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <KTD> Moved drivers inside "C:\D\G\X" to "C:\WINDOWS\System32\Drivers\D\G".
2008-02-18 13:42:36 : <ERR> Could not apply KTD on "C:\D\G\A\3", since it does not exist!
2008-02-18 13:42:37 : <ERR> Could not apply KTD on "C:\D\G\N\3", since it does not exist!
2008-02-18 13:42:37 : <ERR> Could not apply KTD on "C:\D\G\N\4", since it does not exist!
2008-02-18 13:42:38 : <ERR> Could not apply KTD on "C:\D\L", since it does not exist!
2008-02-18 13:42:41 : <KTD> Moved drivers inside "C:\D\M" to "C:\WINDOWS\System32\Drivers\D".
2008-02-18 13:42:41 : <ERR> Could not apply KTD on "C:\D\S\CR\1", since it does not exist!
2008-02-18 13:42:42 : <ERR> Could not apply KTD on "C:\D\S\CR\2", since it does not exist!
2008-02-18 13:42:42 : <ERR> Could not apply KTD on "C:\D\S\CR\3", since it does not exist!
2008-02-18 13:42:43 : <ERR> Could not apply KTD on "C:\D\S\N", since it does not exist!
2008-02-18 13:42:43 : <ERR> Could not apply KTD on "C:\D\S\R", since it does not exist!
2008-02-18 13:42:44 : <ERR> Could not apply KTD on "C:\D\S\V", since it does not exist!
2008-02-18 13:42:44 : <ERR> Could not apply KTD on "C:\D\S\A", since it does not exist!
2008-02-18 13:42:45 : <ERR> Could not apply KTD on "C:\D\S\AV", since it does not exist!
2008-02-18 13:42:45 : <ERR> Could not apply KTD on "C:\D\S\C", since it does not exist!
2008-02-18 13:42:46 : <ERR> Could not apply KTD on "C:\D\S\CI", since it does not exist!
2008-02-18 13:42:46 : <ERR> Could not apply KTD on "C:\D\S\CO", since it does not exist!
2008-02-18 13:42:46 : <ERR> Could not apply KTD on "C:\D\S\CR\4", since it does not exist!
2008-02-18 13:42:47 : <ERR> Could not apply KTD on "C:\D\S\CR\5", since it does not exist!
2008-02-18 13:42:47 : <ERR> Could not apply KTD on "C:\D\S\CR\6", since it does not exist!
2008-02-18 13:42:47 : <ERR> Could not apply KTD on "C:\D\S\E", since it does not exist!
2008-02-18 13:42:47 : <ERR> Could not apply KTD on "C:\D\S\H", since it does not exist!
2008-02-18 13:42:47 : <ERR> Could not apply KTD on "C:\D\S\M", since it does not exist!
2008-02-18 13:42:48 : <ERR> Could not apply KTD on "C:\D\S\S", since it does not exist!
2008-02-18 13:42:49 : <ERR> Could not apply KTD on "C:\D\S\SC", since it does not exist!
2008-02-18 13:42:49 : <ERR> Could not apply KTD on "C:\D\S\SI", since it does not exist!
2008-02-18 13:42:50 : <ERR> Could not apply KTD on "C:\D\S\SM", since it does not exist!
2008-02-18 13:42:50 : <ERR> Could not apply KTD on "C:\D\S\T", since it does not exist!
2008-02-18 13:42:50 : <ERR> Could not apply KTD on "C:\D\S\TR", since it does not exist!
2008-02-18 13:42:50 : <ERR> Could not apply KTD on "C:\D\S\Y", since it does not exist!
2008-02-18 13:42:50 : <ERR> Could not apply KTD on "C:\D\W", since it does not exist!15 2008-02-19 21:49:06
Topic: [Existing Feature] [REQ] 8.3 naming for DP's (14 replies, posted in Feature Requests)
I'd like to see DP Base auto-rename DP's to the 8.3 naming convention automatically into the OEM folder.
During testing of Packs, or if sound, cpu, graphics gets beyond version 9, the install doesn't work, you get file not present when DriverPacks finisher tries moving the flies at end of installation. This occurs becaus they have DPSAymmvv.7z, DPSBymmvv.7z, DPCPymmvv.7z, DPGAymmvv.7z, DPGBymmvv.7z and DPGCymmvv.7z... all of which become 9.3 (or more if testing nightlies) in the event exceeding 9 on the version, which fails during the DOS mode copying. If DP Base auto-renamed them this issue would be resolved.... I'd suggest leaving the version out completely or leaving DP off of the file names and still auto 8.3 correction. Could even make a DP folder inside OEM folder if you wanted ppl to be able to know they are the DP's. The last method would need changes to the presetup.cmd file obviously.
Anyway, just some thoughts running around my head here..... thanks for entertaining me 
16 2008-02-04 05:31:45
Re: Testers Needed (76 replies, posted in News)
Yes, I can also confirm RC2 worked flawlessly.
17 2008-02-03 21:37:05
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
I had to edit the S4 section to include my hardware string id (the &CC_0101 was causing my issues):
ms_1_hwids=....,PCI\VEN_1095&DEV_3512&SUBSYS_35121095,...."
This fixed my BSOD on boot to gui mode. Now there is another issue I am seeing.... MEGAIntel.sys not found, I suspect this MAY be due to not being 8.3 naming (it is 9.3 if my count is correct)
I just edited the DPMS ini file changing the tag from MegaINTEL to MegaINTL... will let you know how that goes...
Editing the tag did correct the MegaINTEL.sys error, so it seems like it was inadvertantly left longer than 8.3
As for the other issue, it was eay enough for me, since that one id string was the only one with subsys_35121095 in the massstorate ini file, another method would have been for to have included my specific hardware id, mine has &Rev1 in it instead of the afformentioned &CC_0101.....
Gotta love the testing....
I can upload my current to nightlies if you want.
18 2008-02-03 21:21:18
Re: Testers Needed (76 replies, posted in News)
is anyone else getting AutoIT error, paramater used without being defined?
19 2008-01-22 07:31:23
Re: Testers needed for new Graphics driverpacks (226 replies, posted in DriverPack Graphics)
@Overflow, the point I was referring to was that you can infact integrate the newer drivers into a previous installation, but will have to update the drivers manually via device manager. But, he can copy the newer driverpack to the OEM folder and have them on the CD. And yes, I understand Finisher only places the drivers into their location and minimal other stuff, that it DOES NOT INSTALL DRIVERS 
Have a great one, and only jokin around with ya on that stuff 
Yes, you can put everything on a DVDRW and refresh it when you want new stuff. I keep several copies on my hard drive, and work on SP2 or SP3 with different things, working on my update packs, drivers, etc. and write the DVDRW that I want.
20 2008-01-21 20:31:19
Re: Testers needed for new Graphics driverpacks (226 replies, posted in DriverPack Graphics)
weltall wrote:
What a lame!!! :$
Why it's not on the site anyway? Hopefully I've waited it before create my installation.
maybe this will be lame also, but.....
The reason some of the updates are not on the main site is because they go through a LOT of testing and revamping before release, to minimize issues for normal users, some of us don't mind blowing up machines a few times for the greater good (error free updated driverpacks)
weltall wrote:
Is there a way to use driverpacks like a post installation? That way I could update it without creating another cd (using a cdrw). I've done this with my softwares, patches and tweaks, I wanted so much to do the same with DP. Is that a way?
Thank you very much!
yes, you can just replace DriverPack Graphics A####.7z on your cdrw in \OEM folder with the new one, and then extract it to your ktd location on your machine. If you search, you will also see a thread about implementing into an already installed machine (Here.)
21 2007-12-28 20:01:02
Re: [IMPLEMENTED] Windows XP Service Pack 3 Support (73 replies, posted in Feature Requests)
@Overflow: I believe that is leftover from early releases of SP3 when it was still just for MSDN and TechNet subscribers.... I have yet to get it to install without asking for CD key during install.
That is exactly why I cam up with the PIDGEN fix, I could not get it to install at all, the keys I use for testing would not work with SP3 when it asked during install.
22 2007-12-25 03:28:11
Re: [IMPLEMENTED] Windows XP Service Pack 3 Support (73 replies, posted in Feature Requests)
OverFlow, I have actually included the PIDGEN trick in one version of my SP3 Update pack
23 2007-12-24 21:40:11
Re: [IMPLEMENTED] Windows XP Service Pack 3 Support (73 replies, posted in Feature Requests)
midiboy wrote:
Hi Overflow !
... and they removed the need to use a serial to install XP (similar to vista).
Has ANYONE acutally tried this method????
I have used a CLEAN XP Corp Vol source (NO SP's at all), no winnt.sif. Just pure source, used MS's integrate option with the SP3 RC1 (have tried this with build 3244 and 3264).
Every time I try to install, it still REQUIRES me to type in a CD key.
lucky2007 wrote:
... I cant test sp3, its only available in English and I got
a small licensing problem with English versions.
got a dutch serial, wont work on English windows.
Fix the licensing issue by copying PIDGEN.DLL from a SP2 source to the I386 folder in your SP3 source after slipstreaming SP3 SP3 will then allow you to use CD Keys that worked with SP2 but won't work with SP3 install, and WGA will still pass if it did before. BTW, the full 336 meg SP3 from MS has all languages in it.
24 2007-12-08 08:27:34
Re: [SOLVED] Recovery and repair Consoles bypassed during setup (18 replies, posted in Software)
Actually, this thread may help a lot in what the original question was concerning...
25 2007-12-02 20:14:19
Re: desktop.ini (7 replies, posted in Feedback and Support - DriverPacks Base)
I believe this is a result of nLite tweaks.
When one sets Windows Explorer to remember each folder's settings, desktop.ini will be in MANY folders. (do a search on the root of your drive including subfolders and system files/folders)
One work around is to then delete all of them listed in the start menu folders in documents and settings (both for the user and all users).
I would try to NOT use those tweaks in nLite and make the changes via Windows Explorer tools/folder options instead, and see if that problem disappears.
You can also uncheck the show hidden, system files, and see if that doesn't help.