jaws1975 - Have you figured out how to include a countdown timer for your version?  I'd really like to have that option, so it could keep the Windows install unattended if the user doesn't deselect certain DriverPacks within the given amount of time.

Thanks Nuno Brito.  I will post in that section the next chance I get.

I will get to work on the tutorial as soon as I get some free time which should be later today, if not, then tomorrow.  Is there a particular section you would like me to post the tutorial in?

@Nuno Brito:  If you are interested, I figured out how to make a multi-boot USB Flash Drive (UFD), so you could have several different versions of say BartPE on one UFD, which is formatted using FAT32.  I have it use FAT32 so you could use drives larger than 4 GB in size, which is a limitation of FAT16X, which PE to USB uses.  At my work, we have UFDs that are 8 GB and needed to get several versions of BartPE to work.  Another reason for making the multi-boot UFD is my work is using PointSec for hard drive encryption and have several different versions of PointSec being used but aren't backwards compatible.  If you would like, I could share this information.  I am a member of Boot Land, so I could post it there if you would like.

80

(210 replies, posted in Software)

WsnoW wrote:

WsnoW -  Thanks.  I will also give this a try.  Does the method your talking about for running from CD/DVD perform automatic installation when the EXE file is run?  If not, how do I do that?

Run application , select DP to unpack & install them. Or U can try to use command line switches for unnattended mode:

DPInstaller_WSED.exe  /untd - this parametr will start Unattended instalation of DP
DPInstaller_WSED.exe  /unth - this parametr will start Unattended instalation of DP by HWIDs

Thanks.  I did some testing of running your application by hand from CD.  I click the "Unpack DP" button and use the 2nd method.  It does everything the way it is supposed to.  I click "Install DP", go through the process, and it works.  I click on "Delete DP" and click "Yes" on the pop-up.  I go to the temp directory for the app (C:\WINDOWS\dp_wsed) and the extracted drivers did not get deleted.

Then, I went onto the CD and ran "clean.cmd" and got "Access is denied." for many of the files it was trying to delete.  I then copied the "clean.cmd" to my desktop to see if I could resolve this and I did.  To resolve the issue, I added a switch to the "del" command.  Here is what the working version I have looks like for that command:

del /s /q /f %WinDir%\dp_wsed > %WinDir%\temp\cln

I added the "/f" switch (without the quotes).  What this switch does is force the deletion of read-only files.  I saved "clean.cmd" after making this change and then ran it.  When I ran it, everything worked perfectly. 

Also, if you don't want/need to have a log file of what was deleted, then you could use just the "rd" command that you have in the "clean.cmd" unchanged and by itself, and it will delete everything including directories, sub-directories, and read-only files without getting an "Access is denied." message.

I hope this feedback helps a little bit.

--Echo_Platoon

81

(210 replies, posted in Software)

Overflow -  Thanks.  I have to try out base version 8.05 to try out that functionality.  I haven't gotten a chance to try out the official release, yet.

WsnoW -  Thanks.  I will also give this a try.  Does the method your talking about for running from CD/DVD perform automatic installation when the EXE file is run?  If not, how do I do that?

82

(210 replies, posted in Software)

I was wondering how I could set this up to run off of CD/DVD.  Thanks in advance.

onyX_12, you could use the installer that WsnoW made.  it is available in the following topic:

http://forum.driverpacks.net/viewtopic.php?id=2403

Thanks, Jaak.  I will helping you out once again in full force as soon as I get rid of this illness, which should be a week or two.  Until then, I will only be able to use half force as I need to rest up a lot to help get rid of the illness.

Sorry about that.

The driver in the [V4] folder works for the user when the user already has Windows installed, but when installing Windows with DriverPacks integrated, textmode doesn't pick up the SATA hard drive at all.  The HWID that would be used for this hardware is "PCI\VEN_1106&DEV_0591&CC_0101".  When I went through the INI file for DP_MassStorage_wnt5_x86-32_8021.7z and looked at the [V4] entry "PCI\VEN_1106&DEV_0591&CC_0101" is not listed there at all.

"PCI\VEN_1106&DEV_0591&CC_0104" is in the [V] entry for DP_MassStorage_wnt5_x86-32_8021.7z INI, but the user isn't using RAID at all.

Also, from reading this whole topic and your posts to me, should I just have the user do the skip method or set ms_count=0 for the relevant section(s) in the INI?  If so, I will make sure these changes happen.

Sorry, I didn't know you were editing your previous post.  To answer your question, I am using DP_MassStorage_wnt5_x86-32_8021.7z.

Cool.  Thanks for the help.  If you would like any help on the forum, feel free to ask me as I should be around more often now until I find out the next event I have to work for my job.

One thing I was wondering, would adding "PCI\VEN_1106&DEV_0591&CC_0101" to the [V4] entry also work in textmode picking up this driver, since this is the correct driver for the hardware?  The current [V4] entry doesn't have it.

Current HWIDs of [V4] entry:

"PCI\VEN_1106&DEV_5372&CC_0101,PCI\VEN_1106&DEV_5337&CC_0101,PCI\VEN_1106&DEV_5287&CC_0101,PCI\VEN_1106&DEV_5324&CC_0101"

One of the users has to get a new motherboard because of physical issues, but the user who I had test the driver in the V4 folder ran what you told me and here are the results for the VIA Bus Master IDE Controller and the VIA Serial ATA Controller

PCI\VEN_1106&DEV_0571&SUBSYS_72551462&REV_07\3&2411E6FE&0&79
    Name: VIA Bus Master IDE Controller - 0571
    Hardware ID's:
        PCI\VEN_1106&DEV_0571&SUBSYS_72551462&REV_07
        PCI\VEN_1106&DEV_0571&SUBSYS_72551462
        PCI\VEN_1106&DEV_0571&CC_01018A
        PCI\VEN_1106&DEV_0571&CC_0101
    Compatible ID's:
        PCI\VEN_1106&DEV_0571&REV_07
        PCI\VEN_1106&DEV_0571
        PCI\VEN_1106&CC_01018A
        PCI\VEN_1106&CC_0101
        PCI\VEN_1106
        PCI\CC_01018A
        PCI\CC_0101

PCI\VEN_1106&DEV_0591&SUBSYS_72551462&REV_80\3&2411E6FE&0&78
    Name: VIA Serial ATA Controller - 0591
    Hardware ID's:
        PCI\VEN_1106&DEV_0591&SUBSYS_72551462&REV_80
        PCI\VEN_1106&DEV_0591&SUBSYS_72551462
        PCI\VEN_1106&DEV_0591&CC_01018F
        PCI\VEN_1106&DEV_0591&CC_0101
    Compatible ID's:
        PCI\VEN_1106&DEV_0591&REV_80
        PCI\VEN_1106&DEV_0591
        PCI\VEN_1106&CC_01018F
        PCI\VEN_1106&CC_0101
        PCI\VEN_1106
        PCI\CC_01018F
        PCI\CC_0101

From what the user told me, the computer only has one hard drive and one DVD/CD drive.  Both seem to be connected via SATA.

I hope this information helps.  Any help is appreciated.  Thanks.

Okay.  Thanks for the information.  It was very helpful.  The two users that I have are only using SATA drives in their systems from what they've told me; I'll have to follow up with them to make sure of this.  As soon as I talk to them on the other forum again, I will have them run the command you mentioned with devcon and then post their results in this topic.  Hopefully, they will be online again soon so I could get back to you as soon as possible.

Sorry for my long absence.  I've been busy working events for my job and more recently have been sick.

On one of the other forums I'm part of, two users came across the issue of "no hard disks to install to" message.  They were both trying to install to SATA hard drives and both had VIA.  So, I had them use sav_HWID to get their HWIDs so I could resolve their issue.

One of the two's HWIDs:

PCI Devices 
=========== 
PCI\VEN_10DE&DEV_01DD&SUBSYS_2810174B&REV_A1\4&204B8D4B&0&0010: NVIDIA GeForce 7500 LE    
PCI\VEN_1106&DEV_0327&SUBSYS_00000000&REV_00\3&2411E6FE&0&00: VIA Standard Host Bridge
PCI\VEN_1106&DEV_0571&SUBSYS_72551462&REV_07\3&2411E6FE&0&79: VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_0591&SUBSYS_72551462&REV_80\3&2411E6FE&0&78: VIA Serial ATA Controller - 0591
PCI\VEN_1106&DEV_1327&SUBSYS_00000000&REV_00\3&2411E6FE&0&01: VIA Standard Host Bridge
PCI\VEN_1106&DEV_2327&SUBSYS_00000000&REV_00\3&2411E6FE&0&02: VIA Standard Host Bridge
PCI\VEN_1106&DEV_287E&SUBSYS_00000000&REV_00\3&2411E6FE&0&8F: VIA Ultra VLINK Controller
PCI\VEN_1106&DEV_3038&SUBSYS_72551462&REV_A0\3&2411E6FE&0&80: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_72551462&REV_A0\3&2411E6FE&0&81: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_72551462&REV_A0\3&2411E6FE&0&82: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_72551462&REV_A0\3&2411E6FE&0&83: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3065&SUBSYS_255C1462&REV_7C\3&2411E6FE&0&90: VIA Rhine II Fast Ethernet Adapter
PCI\VEN_1106&DEV_3104&SUBSYS_72551462&REV_86\3&2411E6FE&0&84: VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3288&SUBSYS_72551462&REV_10\4&65D665F&0&0898: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1106&DEV_3327&SUBSYS_00000000&REV_00\3&2411E6FE&0&03: VIA Standard Host Bridge
PCI\VEN_1106&DEV_3337&SUBSYS_00000000&REV_00\3&2411E6FE&0&88: VIA Standard PCI to ISA Bridge
PCI\VEN_1106&DEV_337B&SUBSYS_00000000&REV_00\3&2411E6FE&0&98: VIA Standard PCI to PCIE Bridge
PCI\VEN_1106&DEV_4327&SUBSYS_00000000&REV_00\3&2411E6FE&0&04: VIA Standard Host Bridge
PCI\VEN_1106&DEV_5327&SUBSYS_00000000&REV_00\3&2411E6FE&0&05: VIA I/O APIC Interrupt Controller
PCI\VEN_1106&DEV_6327&SUBSYS_00000000&REV_00\3&2411E6FE&0&06: VIA Security Device
PCI\VEN_1106&DEV_7327&SUBSYS_00000000&REV_00\3&2411E6FE&0&07: VIA Standard Host Bridge
PCI\VEN_1106&DEV_A327&SUBSYS_00000000&REV_00\3&2411E6FE&0&10: VIA PCI to PCI Bridge Controller
PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_00\3&2411E6FE&0&08: VIA CPU to AGP2.0/AGP3.0 Controller
PCI\VEN_1106&DEV_C327&SUBSYS_00000000&REV_00\3&2411E6FE&0&18: VIA PCI to PCI Bridge Controller
PCI\VEN_1131&DEV_7133&SUBSYS_001016BE&REV_D1\3&2411E6FE&0&50: Creatix SAA7131, Hybrid Capture Device

Second of the two's HWIDs:

PCI\VEN_1002&DEV_7187&SUBSYS_0920174B&REV_00\4&204B8D4B&0&0010: Radeon X1300 Series    
PCI\VEN_1002&DEV_71A7&SUBSYS_0921174B&REV_00\4&204B8D4B&0&0110: Radeon X1300 Series Secondary 
PCI\VEN_10EC&DEV_8167&SUBSYS_816710EC&REV_10\4&71586A9&0&3899: Realtek RTL8169/8110 Family Gigabit Ethernet NIC
PCI\VEN_1106&DEV_0327&SUBSYS_00000000&REV_00\3&2411E6FE&0&00: VIA Standard Host Bridge
PCI\VEN_1106&DEV_0571&SUBSYS_81CF1043&REV_07\3&2411E6FE&0&79: VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_0591&SUBSYS_81CF1043&REV_80\3&2411E6FE&0&78: VIA Serial ATA Controller - 0591
PCI\VEN_1106&DEV_1327&SUBSYS_00000000&REV_00\3&2411E6FE&0&01: VIA Standard Host Bridge
PCI\VEN_1106&DEV_2327&SUBSYS_00000000&REV_00\3&2411E6FE&0&02: VIA Standard Host Bridge
PCI\VEN_1106&DEV_287E&SUBSYS_00000000&REV_00\3&2411E6FE&0&8F: VIA Ultra VLINK Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_A0\3&2411E6FE&0&80: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_A0\3&2411E6FE&0&81: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_A0\3&2411E6FE&0&82: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_A0\3&2411E6FE&0&83: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_86\3&2411E6FE&0&84: VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3288&SUBSYS_82491043&REV_10\3&2C8B7305&0&08: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1106&DEV_3327&SUBSYS_00000000&REV_00\3&2411E6FE&0&03: VIA Standard Host Bridge
PCI\VEN_1106&DEV_3337&SUBSYS_00000000&REV_00\3&2411E6FE&0&88: VIA Standard PCI to ISA Bridge
PCI\VEN_1106&DEV_337A&SUBSYS_00000000&REV_00\3&2411E6FE&0&99: VIA Standard PCI to PCI Bridge
PCI\VEN_1106&DEV_337B&SUBSYS_00000000&REV_00\3&2411E6FE&0&98: VIA Standard Host Bridge
PCI\VEN_1106&DEV_4327&SUBSYS_00000000&REV_00\3&2411E6FE&0&04: VIA Standard Host Bridge
PCI\VEN_1106&DEV_5327&SUBSYS_00000000&REV_00\3&2411E6FE&0&05: VIA I/O APIC Interrupt Controller
PCI\VEN_1106&DEV_6327&SUBSYS_00000000&REV_00\3&2411E6FE&0&06: VIA Security Device
PCI\VEN_1106&DEV_7327&SUBSYS_00000000&REV_00\3&2411E6FE&0&07: VIA Standard Host Bridge
PCI\VEN_1106&DEV_A327&SUBSYS_00000000&REV_00\3&2411E6FE&0&10: VIA PCI to PCI Bridge Controller
PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_00\3&2411E6FE&0&08: VIA CPU to AGP Controller
PCI\VEN_1106&DEV_C327&SUBSYS_00000000&REV_00\3&2411E6FE&0&18: VIA PCI to PCI Bridge Controller
PCI\VEN_197B&DEV_2363&SUBSYS_2363197B&REV_02\4&14CAA1A9&0&0018: JMicron JMB36X Controller

So, the HWIDs relevant to this issue are PCI\VEN_1106&DEV_0591&SUBSYS_81CF1043&REV_80 and PCI\VEN_1106&DEV_0591&SUBSYS_72551462&REV_80

I saw that the driver in the V4 folder had PCI\VEN_1106&DEV_0591&CC_0101.  I sent this folder to one of the users and had the user do an "Update Driver" with this driver.  This driver worked.  I went on to look at the DP_MassStorage INI file and saw that the PCI\VEN_1106&DEV_0591&CC_0101 wasn't in the V4 entry, but saw a similar HWID of PCI\VEN_1106&DEV_0591&CC_0104 in the V entry.

I'm guessing that the two similar HWIDs conflict with each other.  Would these users have to modify the DP_MassStorage INI to suit their needs?

I was looking through some of the network drivers and found that some of the Intel network drivers have files with the same name.  This occurs in the following Intel driver folders:

I\PRO100
I\PRO1000
I\PROSETDX
I\PROXGB

Some of the same filenames are:

PROUnstl.exe
NicCo.dll
NicCO6.dll
NicInE6.dll
NicInstE.dll
NicInst.dll

I'm not sure if these will need to be made into unique filenames for when network drivers are used in BartPE, but I did want to bring it up just in case.

@Overflow:  That is weird because the description on Promise's website says the driver is for Windows XP/2003.

This is from the description on Promise's website:

This is the updated release and Microsoft WHQL Logo driver for Windows XP/2003 (32/64-bit)
- fixes auto-rebuild from free disk
- change default setting of auto rebuild from spare to spare and free disks.

JakeLD wrote:

I will take care of it, thx Platoon. Did you do a search for the inf and sys file name to make sure they are not duplicated ?

I just did a search for the INF and SYS files in the directory of the MassStorage DriverPack nightly and there are no duplicates for either.

@Jaak:  Here is the driver.  It is pretty much set to be put into the DriverPack.  I did a search for each of the HWIDs for this in the INI file of the current MassStorage DriverPack nightly and didn't find anything with the same name.  In the 7-zip file, there is a "for_INI.txt" file in there for the INI entry.  I gave it its unique ID and it is only six characters long so it is compatible with the standard.  Also did a search for the unique ID and found nothing with the same name.  I had it skip if the OS is w2k, since this driver is only for XP and 2k3.  Please just review it to make sure there isn't something I missed.  Thanks.

http://rapidshare.com/files/84295048/FastTrak_TX4310.7z

95

(1 replies, posted in DriverPack LAN)

Here is the nforce 780i LAN driver that I extracted from the chipset package.  There are two downloads that I am providing.  One is the unedited version, which is how it comes with the chipset package.  The other is with the edited version, where the files are renamed and references in the INFs updated to reflect these changes.  The second one is for temporary use in BartPE until the BartPE LAN plugin comes out.  The only reason why the files are so big is because I didn't delete the NAMSetup.exe files in the NAM folders, which take up almost all of the size.

I'm not sure if these were included in the LAN DriverPack yet or in the nightly LAN DriverPack, but here they are.

DriverVer = 10/12/2007, 67.6.7

Unedited:

http://rapidshare.com/files/83016740/nforce780_unedited.7z

Edited:

http://rapidshare.com/files/83018017/nforce780_edited.7z

I knew it wasn't going to be an official plugin.  I don't mind you being a kill joy because I don't like acting all high and mighty.

@OverFlow:  So, are we going to definitely use the Joshua plug-in for nvidia drivers for BartPE and eliminate the nvidia drivers we have in the LAN DriverPack just for BartPE?  I actually had my brother-in-law try Joshua's plug-in and it still didn't work on this machine.

I think I found an issue with some of the nvidia LAN drivers in BartPE

My brother-in-law was testing out his BartPE on an HP xw9300 workstation to see if the LAN drivers get picked up and the drivers didn't get picked up.  I had him going into Windows and run the sav_HWID on the machine so I could search the drivers for the one that had the matching HWID for the LAN.  I found the shortened version of the proper HWID (up to DEV_XXXX but containing anything after that such as &SUBSYS).  I thought that it should have picked it up, but it didn't.  What I did was took the full HWID, which ended with &REV_A3, and added it into the INF files.  Then, I had my brother-in-law build BartPE, burn the ISO, and test it.  This time it picked up the LAN driver.

Sorry if I don't have the HWID in this.  I have it in my work e-mail at the moment and won't access it again until I go in on Monday.  I will post the HWID on Monday so I could make my point clearer.

--Echo_Platoon

@Jaak:  How is everything coming along with this?

OverFlow wrote:

Congratulations on your promotion Corporal Echo_Platoon

Thanks for the promotion.