The nightlies website went down before I ever got a chance. Haven't been able to find it since then.
But I'm confident it works. Sounds like it was an easy fix.
Thanks a bunch for the help.
(apologies for the very delayed response.)
26 2010-06-04 05:28:22
Re: [IMPL] BASE textmode integration deletes certain textmode entries (14 replies, posted in Feedback and Support - DriverPacks Base)
27 2010-01-14 06:57:18
Re: Quick question: How is the PhysX installer launched? (7 replies, posted in DriverPack Graphics)
I still squeeze everything onto a 700MB disc. I like to keep it old school.
Anyway, thanks for testing and helping me out. If you guys change your mind, you're more than welcome to use the pack however you please.
28 2010-01-11 14:23:10
Re: Quick question: How is the PhysX installer launched? (7 replies, posted in DriverPack Graphics)
Having the file repeated three times in a single archive doesn't noticeably increase the size of the archive. The problem is that the Nvidia installer uses terrible compression, and it can't be compressed down much more due to the Shannon limit (I think you guys have it going from 35MB down to 30MB or something). By decompressing everything, I am able to then compress it the right way down to 8-9MB (down from a whopping 100MB or so). I made it into a "multimode" application because those are what I prefer.
Anyway, a couple of questions/ideas:
- Does my modification break the signature of the driver?
- Do you want me to change anything about PhysX_9.09.1112_SystemSoftware.exe? I can make it look for PhysX.exe, or I can make it do stuff with command-line paramters, check the registry, or whatever. As of right now, it's literally one line of code with zero fail-safe. If PhysX.exe isn't present, then it will return an error alert. While this isn't a problem on a fresh install, it might cause problems with KTD if a person deletes physx.exe, but the "dummy" file remains in tact.
29 2010-01-10 12:12:17
Re: Quick question: How is the PhysX installer launched? (7 replies, posted in DriverPack Graphics)
I don't have an Nvidia card.
Anyone want to give it a shot?
Download: http://xp.xpdnc.org/temp/DP_Graphics_Ph … 001dd1a.7z
md5: 0746926668f9c9cf0e6fe23544447318
compressed: 9.2MB | decompressed: 10.6MB
What's in it:
%SystemDrive%\D\
%SystemDrive%\D\G\
%SystemDrive%\D\G\PhysX.exe
%SystemDrive%\D\G\N1\
%SystemDrive%\D\G\N1\PhysX_9.09.1112_SystemSoftware.exe
%SystemDrive%\D\G\N3\
%SystemDrive%\D\G\N3\PhysX_9.09.1112_SystemSoftware.exe
%SystemDrive%\D\G\NM\
%SystemDrive%\D\G\NM\PhysX_9.09.1112_SystemSoftware.exePhysX_9.09.1112_SystemSoftware.exe will execute the following:
..\PhysX.exe -ai30 2010-01-10 10:30:08
Re: Quick question: How is the PhysX installer launched? (7 replies, posted in DriverPack Graphics)
Gah! No wonder nothing was turning up.
Do you know if there is an easy way to change the command line that's actually passed to launch the installer? (the one above simply tells it to instantiate the installer, but it doesn't lead to the command line that's executed)
Basically, what I'm doing is pulling the MSI out of the installer EXE, then doing an admin install of the MSI, and repackaging it. This should significantly reduce the size of my PhysX DriverPack. But in order to do it, I need to change the command-line to execute my MSI instead of Nvidia's EXE.
Any ideas?
edit--
On second thought, I could actually do what you guys do with SETUP.EXE, and just create an EXE file that tells it to execute my MSI file at a specified time or upon a specified trigger. That would probably be better anyway because it would significantly reduce the amount of space that's taken up when the files are extracted (since the MSI would only have to appear once in the DriverPack).
I'll toy around with it and see what I can come up with.
31 2010-01-10 10:08:36
Topic: Quick question: How is the PhysX installer launched? (7 replies, posted in DriverPack Graphics)
I can't figure out where you actually have the command set to launch PhysX, and what sets that command. I'd imagine that it would all start at BASE or DPsFnshr because PhysX doesn't have an INI file with it, so something has to detect that it's there. What is it?
32 2009-12-07 12:08:47
Re: Release Candidates of Graphics DriverPacks open for public testing! (41 replies, posted in News)
Just to clarify, is that typo fixed in the current rc11? If not, can you tell me what it was so I can fix it on my end? I'm going to be doing some driver testing over the next couple weeks due to an influx of incoming units coming in need of reformatting.
33 2009-12-07 07:32:11
Re: Release Candidates of Graphics DriverPacks open for public testing! (41 replies, posted in News)
Are the recent release candidates (rc11 and rc10) more stable than the release candidates listed in the first post (rc9 and rc10)?
34 2009-11-03 06:39:23
Re: [CLSD] Graphics BETA DriverPacks are here...for TESTING purposes only! (5 replies, posted in DriverPack Graphics)
I used GA on my buddy's computer last night. NVidia GTS250 was recognized by Windows (wasn't "unknown device"), but the drivers were insufficiently installed. We were in a hurry, so I didn't look into what exactly happened, but I will say that I wasn't capped at 800x600 resolution, but it wouldn't go up to the maximum resolution supported. None of the proprietary NVidia software installed. I just went to the NVidia website, downloaded the latest stuff, and it worked fine.
On a side note, where do I put the PhysX pack? Does that go in DriverPacks folder, or does it go in the 3rd Party folder?
35 2009-10-27 04:52:26
Re: [IMPL] BASE textmode integration deletes certain textmode entries (14 replies, posted in Feedback and Support - DriverPacks Base)
oh yeah. lol.
I submitted a formal bug report. I marked it as "major" since it yields a non-functional disc, but perhaps it's a "minor" issue because it's very uncommon.
Keep me posted on what happens, yeah? I'm at least interested in confirming that it's not just me.
36 2009-10-26 11:45:44
Re: Driverpack Userbars! (36 replies, posted in Other)
lol. I thought "ADMIN" said "ROMIN." 
It wasn't until I saw Overflow post that I realized what it said.
My eyes must have been broken because I can totally see "admin" now.
37 2009-10-26 09:51:23
Re: [IMPL] BASE textmode integration deletes certain textmode entries (14 replies, posted in Feedback and Support - DriverPacks Base)
I'm updating a bunch of programs for another disc right now. Once I finish, I'll make a new ISO and run DP again but with the debug option. I'll give you a full a log. Until then, here's my AddOn: http://xp.xpdnc.org/files/AddOns/UltraD … 0.17.0.zip
[offtopic] I do recommend using that defrag program. It's pretty awesome. It's open source and has offline defrag support. That's not to mention that it weighs in at under 1MB. [/offtopic]
38 2009-10-26 08:23:37
Re: [IMPL] BASE textmode integration deletes certain textmode entries (14 replies, posted in Feedback and Support - DriverPacks Base)
Definitely not. I had run it through many times completely from scratch, and when I say "from scratch," I mean from extracting the TechNet ISO (SHA1: 66ac289ae27724c5ae17139227cbe78c01eefe40) to RVMi with just my addon, to DriverPacks BASE.
But just for you, I ran it again on an install I created with all of my updates and whatnot. As you'll see below, no previous driver packs had been integrated. Upon using DriverPacks BASE to integrate some driverpacks, the entries for my defragmenting program are removed from TXTSETUP.SIF.
DPs_BASE.log
2009-10-25 13:29:45 : <INIT> DriverPacks BASE 9.02.0.1 initialized.
2009-10-25 13:29:45 : <INIT> Host environment: WIN_XP Service Pack 2 X86 on a X86 CPU.
2009-10-25 13:29:45 : <INIT> Created temporary working directory.
2009-10-25 13:29:45 : <INIT> Imported proxy settings from Internet Explorer.
2009-10-25 13:29:45 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-10-25 13:29:45 : <INIT> Detected DriverPack Chipset 909r1!
2009-10-25 13:29:45 : <INIT> Detected DriverPack CPU 90701!
2009-10-25 13:29:45 : <INIT> Detected DriverPack Graphics A 910rc1!
2009-10-25 13:29:45 : <INIT> Detected DriverPack Graphics B 910rc1!
2009-10-25 13:29:45 : <INIT> Detected DriverPack Graphics C 910rc1!
2009-10-25 13:29:45 : <INIT> Detected DriverPack LAN 908n3!
2009-10-25 13:29:45 : <INIT> Detected DriverPack MassStorage 909r6!
2009-10-25 13:29:45 : <INIT> Detected DriverPack Sound A 90902!
2009-10-25 13:29:45 : <INIT> Detected DriverPack Sound B 90903!
2009-10-25 13:29:45 : <INIT> Detected DriverPack WLAN 90807!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Bluetooth 081028!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Broadband 70416!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Graphics A PhysX 906!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Graphics Languages 906!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack HID 90813!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Input 070923!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Misc 90813!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Modem 90805!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Monitor 90808!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Phone 80207!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack PrintersCanonInkjet 61105!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack PrintersCanonLaserjet 61020!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack PrintersHP 71126!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Scanner 60831!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack SmartCardReader 80228!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack TouchScreen 708!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack TV 90812!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack USB 80911!
2009-10-25 13:29:45 : <INIT> Detected 3rd Party DriverPack Virtual 90225!
2009-10-25 13:29:46 : <INIT> Detected 3rd Party DriverPack WebCam 90706!
2009-10-25 13:29:46 : <INIT> Finished scanning.
2009-10-25 13:29:46 : <INIT> Detected settings file "F:\DDUXPCD\DriverPacks\DPs_BASE.ini".
2009-10-25 13:29:46 : <INIT> wnt5_x86-32_StandAloneDrivers is the selected installation platform .
2009-10-25 13:29:46 : <INIT> Imported settings from settings file.
2009-10-25 13:29:46 : <GUI> Initialized GUI.
2009-10-25 13:29:46 : <GUI> Created a list of all available language files.
2009-10-25 13:29:46 : <GUI> Set the last used language, English, as the GUI language.
2009-10-25 13:29:50 : <GUI> Refreshed UpdateChecker with success.
2009-10-25 13:30:01 : <GUI> No OS could be detected.
2009-10-25 13:30:01 : <GUI> any_any_any is the selected installation platform .
2009-10-25 13:30:01 : <GUI> Changed installation platform from "StandAloneDrivers" to "disc".
2009-10-25 13:30:15 : <GUI> Changed Windows installation files OR export (depending on the installation platform) location to F:\DDUXPCD\WinXP_wSP3.
2009-10-25 13:30:15 : <GUI> Windows XP Professional - Retail SP3 detected.
2009-10-25 13:30:15 : <GUI> wnt5_x86-32_disc is the selected installation platform .
2009-10-25 13:31:24 : <GUI> Exported settings to F:\DDUXPCD\DriverPacks\MassStorage-NoKTD-NoQSC-NoROE.ini.
2009-10-25 13:31:30 : <GUI> Saved settings!
2009-10-25 13:31:30 : <GUI> Closed GUI.
2009-10-25 13:31:30 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m2.
2009-10-25 13:31:35 : <PREP> Removed all attributes from \I386.
2009-10-25 13:31:35 : <PREP> No previous DriverPacks installation found, Prep stage will be skipped
2009-10-25 13:31:46 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2009-10-25 13:31:46 : <SLIP> F:\DDUXPCD\DriverPacks\tmp\DPMtmp\DriverPack_MassStorage_wnt5_x86-32.ini
2009-10-25 13:31:48 : <SLIP> Processing the files now. This may take a minute.
2009-10-25 13:32:22 : <SLIP> Slipstreamed DriverPack MassStorage text mode driver files.
2009-10-25 13:32:22 : <SLIP> txtsetup.sif Backed-up Successfully
2009-10-25 13:32:22 : <SLIP> dosnet.inf Backed-up Successfully
2009-10-25 13:32:32 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2009-10-25 13:32:33 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2009-10-25 13:33:53 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2009-10-25 13:33:53 : <SLIP> Created necessary directory structure for method 2.
2009-10-25 13:33:53 : <SLIP> Copying files necessary for method 2.
2009-10-25 13:33:54 : <SLIP> Extracted additional files necessary for method 2.
2009-10-25 13:33:54 : <SLIP> expanded setup.ex_ to setuporg.exe
2009-10-25 13:33:54 : <SLIP> SETUP.EX_ Backed-up Successfully
2009-10-25 13:33:55 : <SLIP> Compressed setup.exe to SETUP.EX_.
2009-10-25 13:33:55 : <SLIP> Method 2 setup.ex_ installed
2009-10-25 13:33:55 : <SLIP> Created \I386\presetup.cmd file.
2009-10-25 13:33:55 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2009-10-25 13:33:55 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2009-10-25 13:33:55 : <SLIP> Copied DriverPack MassStorage to \OEM.
2009-10-25 13:33:55 : <SLIP> Copied DriverPacks to \OEM.
2009-10-25 13:33:55 : <SLIP> Will not slipstream patches, Service Pack 3 was detected.
2009-10-25 13:33:55 : <SLIP> Will not slipstream KB888111 because no Sound DriverPack is being slipstreamed
2009-10-25 13:33:55 : <SLIP> Will not slipstream KB883667 because no Graphics DriverPack is being slipstreamed
2009-10-25 13:33:55 : <SLIP> WINNT.SIF Backed-up Successfully
2009-10-25 13:33:55 : <SLIP> Updated \I386\winnt.sif to support method 2.
2009-10-25 13:33:55 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2009-10-25 13:33:56 : <SLIP> DP_Install_Tool was copied successfully
2009-10-25 13:33:56 : <SLIP> Slipstream finished in 2 minutes and 26 seconds.
2009-10-25 13:33:58 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"
[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "F:\DDUXPCD\WinXP_wSP3"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "custom"
; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "no"
; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "no"
DP_CPU = "no"
DP_Graphics_A = "no"
DP_Graphics_B = "no"
DP_Graphics_C = "no"
DP_LAN = "no"
DP_MassStorage = "yes"
DP_Sound_A = "no"
DP_Sound_B = "no"
DP_WLAN = "no"
DPs_3rd_party = "no"
DP_MassStorage_textmode = "yes"
; this section is optional!
[OptionalSettingsOther]
; CCC/CCP/None, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming Graphics DriverPack)
; 1/2/3/None, use Nvidia Control Panel - 1 = Old, 2 = New, 3 = Both, None
ATI_cpl = "CCC"
Nvidia_cpl = "2"
2009-10-25 13:33:59 : <CLNP> Create a DPs_Base.log backup @ F:\DDUXPCD\DriverPacks\LogFiles\DPs_BASE_09-10-25_13-33.log
2009-10-25 13:33:59 : <CLNP> Program terminated.-- link/image removed because I deleted the files on my server to avoid clutter --
My conclusion is that it's a bug. I'm more than willing to provide you with my AddOn if you want to test it yourself. For now I'm just integrating the AddOn after DriverPacks BASE and all is well.
39 2009-10-23 14:17:10
Re: ASUS P5N7A-VM - NVIDIA GeForce 9300 / nForce 730i - SATA Problem (35 replies, posted in DriverPack Mass Storage)
Yeah, it would go in i386. Just like the Hive___.inf files, it can't be compressed either.
Here is an example of a quick Addon that I created. This should work with RVMi for sure, and I believe that it will also work with nLite.
http://xp.xpdnc.org/temp/nvgts_textmode_fixes.7z
Examine both files contained within it if you want to know how it ticks. Also feel free to change the version info in the INF file.
I will add that Base has gotten pissy in the past when I've added INFs to be processed during textmode setup. I'm not sure what causes the issue, but if you get an error similar to mine in that thread, just process that single file in RVMi after you've run Base.
40 2009-10-23 08:36:06
Re: ASUS P5N7A-VM - NVIDIA GeForce 9300 / nForce 730i - SATA Problem (35 replies, posted in DriverPack Mass Storage)
If you want to do it in a more "clean" fashion, you can edit your TXTSETUP.SIF file to include a separate INF just for adding the nVidia registry settings.
In TXTSETUP, look for [HiveInfs.Fresh], and add: AddReg = nvgts.inf,AddReg
Add that entry to [HiveInfs.Upgrade] as well if you want.
Now make sure you have the proper entries earlier in TXTSETUP: nvgts.inf = 100,,,,,,_x,,3,3
And add the entry to DOSNET: d1,nvgts.inf
Then you just create your nvgts.inf file with the registry entries in it. Be sure to make the registry section name "AddReg" or otherwise change it in the TXTSETUP HiveInfs secion(s).
If you really want, I can create an RVMi/nLite addon to do it.
41 2009-10-15 05:02:01
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
What I'm saying is that with this device: PCI\VEN_8086&DEV_27C5&CC_0106 (the Intel device)
- I get a BSOD when used with IaStor Version 7.8.0.1012
- I get a BSOD when used with IaStor Version 8.9.2.1002
- The device works fine with IaStor Version 8.6.0.1007
HOWEVER, when I use DP_MassStorage_wnt5_x86-32_909r6 -- the one that contains IaStor Version 8.6.0.1007 -- I get a BSOD for this device: PCI\VEN_104C&DEV_803B (the card reader; TXN device)
The drivers for the TXN device have always installed just fine in the past. But when used with DriverPacks, it causes the driver to not install, and then when the vendor's driver is applied, I get a BSOD on next reboot.
The problem with the TXN device might have been a fluke. It could be caused by a different DP. It could be something else. I haven't looked into it too deeply. I'll check it out today and report back.
42 2009-10-12 03:11:21
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
My confusion comes from this, though...
PCI\VEN_8086&DEV_27C5&CC_0106 ................ works with 8.6.0.1007
BUT...
PCI\VEN_104C&DEV_803B&SUBSYS_2081107B&REV_00\4&6B16D5B&0&4AF0 .................. shows up as a Mass Storage device with no drivers, and when I install vender's recommended drivers for it, I get a blue screen.
It's like out of the frying pan and into the fire. That's why I listed 8.6x as "partially" compatible.
I've been fairly busy lately. I'll eventually get it all figured out.
I'll definitely let you guys know when I get everything working flawlessly.
43 2009-10-04 09:47:58
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
If you're talking about the Nightlies then yeah.
See post #10 of this thread. The DP MS versions that I tried are on the right. "DP_MassStorage_wnt5_x86-32_909r6" is the latest Nightly, which has my device associated with v8.9. That version was actually worse than the latest stable, though, because textmode didn't even recognize my hard drive.
44 2009-10-04 05:27:26
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
I didn't mess with any of it. I just added the MS pack as usual. When I left out the DriverPacks and integrated just the standalone 6x driver, it all worked flawlessly.
I'll try editing the MS INI file and creating a new IA directory and sticking my driver in that.
45 2009-10-03 12:42:19
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
Update
Intel SATA AHCI/RAID
Device: PCI\VEN_8086&DEV_27C5&CC_0106
Version 5.5.0.1035 ---- UNTESTED
Version 6.2.0.2002 ---- COMPATIBLE
Version 7.0.0.1020 ---- UNTESTED
Version 7.8.0.1012 ---- INCOMPATIBLE [DP_MassStorage_wnt5_x86-32_901r3]
Version 8.6.0.1007 ---- PARTIALLY COMPATIBLE [DP_MassStorage_wnt5_x86-32_901]
Version 8.9.2.1002 ---- INCOMPATIBLE [DP_MassStorage_wnt5_x86-32_909r6]
OK, so 8.6x seemed to get textmode to see my hard drive (8.9x didn't), and my computer is no longer in an endless BSOD loop (which is what happened with the 7.8x release). So it worked in that regard.
HOWEVER
the Mass Storage Controller driver in Windows was not recognized.
PCI\VEN_104C&DEV_803B&SUBSYS_2081107B&REV_00\4&6B16D5B&0&4AF0
46 2009-10-03 12:09:14
Topic: [IMPL] ZD1211BU drivers are outdated (1 replies, posted in DriverPack WLAN)
Current version with latest WLAN stable and WLAN beta: 08/17/2005,5.2.0.0
Here is the one that I have.
http://xp.xpdnc.org/ZD1211BU.7z
01/10/2006,6.3.2.15
47 2009-09-15 04:07:48
Re: [IMPL] BASE textmode integration deletes certain textmode entries (14 replies, posted in Feedback and Support - DriverPacks Base)
Your analysis of the file is what I figured the BASE (I'm using the latest Nightlies, by the way; I should have mentioned that) was doing as well. The file looks like it's not needed, but it actually is. You can actually add entries to the Windows Registry during TEXTMODE setup.
Other examples:
hivecls.inf = 100,,,,,,_x,,3,3
hivedef.inf = 100,,,,,,_x,,3,3
hivesft.inf = 100,,,,,,_x,,3,3
hivesys.inf = 100,,,,,,_x,,3,3BASE doesn't touch those, however.
"Breaking the rules" solved the issue. If you're still interested in troubleshooting it, however, I can get you the DIFF and LOG files that you're requesting. I'd like to wait until I get my laptop (the one mentioned in my other thread) up and running before I do that, however, because the computer I'm on is an Athlon XP 2600+ 
.
edit--
Also, _x means that the file is not compressed (it's *.INF not *.IN_). So yes, in a manner of speaking, that can be translated as "Source is a Windows CD," but I never really thought of it like that. It makes sense, though.
edit2--
There is also an associated *.SYS file with the INF. There is ultradfg.INF and ultradfg.SYS. I'm integrating Ultra Defrag 3.
48 2009-09-14 14:15:42
Topic: [IMPL] BASE textmode integration deletes certain textmode entries (14 replies, posted in Feedback and Support - DriverPacks Base)
Hello, me again!
I wrote an Addon Pack that integrates an INF file during textmode, but DriverPacks seems to be interfering with it.
I made an ISO, everything worked fine in the VM. No errors in the setup log. Everything was perfect.
Then when I integrated DriverPacks, I got this:
Naturally, I checked SourceDiskFiles, and apparently DriverPacks BASE is removing the reference to it from that section. Here is how it's referenced:
ultradfg.inf = 100,,,,,,_x,,3,3BASE seems to be removing that line, for whatever reason. I'm guessing it has something to do with (a) the file isn't compressed, and (b), the file isn't copied to the local drive (e.g., the INF folder). I tried renaming the file to *.SIF to see if that would fix the issue, and it didn't. So I renamed it to *.WTF, and that didn't work either. So BASE isn't freaking out on the filetype. It's getting angry with the entry itself.
I've tested this precise issue at least half a dozen times. I'm positive it's DP Base that's causing the problem.
If it helps, this is where I'm using the INF file (these sections are in TXTSETUP.SIF):
[HiveInfs.Fresh]
AddReg = hivedef.inf,AddReg
AddReg = hivesys.inf,AddReg
AddReg = hivesft.inf,AddReg
AddReg = hivecls.inf,AddReg
AddReg = hiveusd.inf,AddReg
AddReg = dmreg.inf,DM.AddReg
AddReg = ultradfg.inf,UD.AddReg
[HiveInfs.Fresh.RemoteBoot]
AddReg = hivesys.inf,AddReg.RemoteBoot
[HiveInfs.Upgrade]
DelReg = hivesft.inf,DelRegFirst
DelReg = hivedef.inf,DelReg
AddReg = hivedef.inf,AddReg
DelReg = hivesys.inf,DelReg
AddReg = hivesys.inf,AddReg
AddReg = hivesys.inf,AddReg.Upgrade
DelReg = hivesft.inf,DelReg
AddReg = hivesft.inf,AddReg
AddReg = hivesft.inf,AddReg.Upgrade
DelReg = hivecls.inf,DelReg
AddReg = hivecls.inf,AddReg
AddReg = hiveusd.inf,AddReg
DelReg = dmreg.inf,DM.DelReg
AddReg = dmreg.inf,DM.AddReg
AddReg = ultradfg.inf,UD.AddRegHere are the contents of the INF file:
[Version]
Signature = "$Windows NT$"
DriverVer=05/13/2009,3.1
[UD.AddReg]
HKLM,"SYSTEM\CurrentControlSet\Services\ultradfg",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Services\ultradfg","DisplayName",0x00000000,"Ultra Defrag"
HKLM,"SYSTEM\CurrentControlSet\Services\ultradfg","ErrorControl",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Services\ultradfg","ImagePath",0x00020000,"system32\DRIVERS\ultradfg.sys"
HKLM,"SYSTEM\CurrentControlSet\Services\ultradfg","Start",0x00010001,3
HKLM,"SYSTEM\CurrentControlSet\Services\ultradfg","Type",0x00010001,1
HKLM,"SYSTEM\CurrentControlSet\Control\CrashControl","AutoReboot",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG","NextInstance",0x00010001,1
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000","Class",0x00000000,"LegacyDriver"
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000","ClassGUID",0x00000000,"{8ECC055D-047F-11D1-A537-0000F8753ED1}"
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000","ConfigFlags",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000","DeviceDesc",0x00000000,"Ultra Defrag"
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000","Legacy",0x00010001,1
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000","Service",0x00000000,"ultradfg"
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000\Control",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000\Control","*NewlyCreated*",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ULTRADFG\0000\Control","ActiveService",0x00000000,"ultradfg"49 2009-09-07 07:15:46
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
Update
I'm pretty sure I've narrowed it down to AHCI. Specifically, this entry in the iaahci.inf file:
[HardwareIds.scsi.iaAHCI_ICH7M]
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"That's the device ID that I have (seen above), and that device ID shows up in the DriverPacks Mass Storage INI file under the iastor 7.8 entry on my disc, but it has since been moved to the iastor 8.6 entry in the latest DriverPack releases.
I'll go ahead and try a newer pack, if that works, then this will be resolved. If that doesn't work, what do I do? Move the device ID to the iastor 7.0 entry (in the Mass Storage INI file) and edit the INF files accordingly? Or do I create a whole new entry just for this device and call the directory IA6 or something?
I'm gonna nip this bitch in the bud, just you wait and see!
50 2009-09-06 19:54:24
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
I read all of that just now, but I'm still not really too sure where I should be starting. Do I add my HWID to the current DriverPack? Or do I add the driver I have (the one from Gateway) to the DriverPack in a new folder?
I see the problem, by the way. The version of iastor offered by Gateway is v6. You guys are using versions 5, 7, and 7+ or something like that. 6x is skipped. I suppose I could see what version my Vista PE disc is using, since my laptop seems to have no problem booting to that.