Jump to content

kickarse

Member
  • Posts

    229
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by kickarse

  1. v.5 - 2009-06-12

    + Fixed issues with DevicePath registry settings, will revert back to original location previous to DriverForge installation

    - Removed Pre and Post scripts, users can do that with a batch and automation

    - Fixed GUI wording

    + Added an option to add default Windows DevicePath to registry

    + Made all files install to Temp folder

    + Fixed edit code to delete all installed temp files

    I'll be releasing the code shortly.

  2. good job for DriverForge, I'm just trying with driverpack and it's seems to run great.

    What about Check_For_Wizard_Title in .ini ? I must replace english text to my localized french native language ? If yes, can you post screenshot of what text replace ?

    Yes you would take out what's there now and localize it to your own language.

    Please let me know what features you'd like to be added. We'll see if we can't add them for you.

    Ability to scan in parent dir sub folders for compressed drivers in said sub folders.

    I can do that :)

    How can I use the Post_Script Feature?

    My Script will started with

    C:\WINDOWS\CSCRIPT.EXE C:\NETINST\postinst.js

    What are the Post_Script Settings for that? What is important?

    Add it C:\Netint\postinst.js to the Switches part of the section. So Post_Script_Switches=C:\Netint\postinst.js

  3. That's not actually correct (then again I'm not a lawyer)...

    The only thing I can find that would stipulate anything about hosting the source is documented at the Terms of Use stating

    "© you have fully complied with any third-party licenses relating to Your Content, agree to pay for all royalties, fees and any other monies owning any person by reason of any of Your Content that you posted to or through SourceForge.net;"

    and "For the SourceForge Site SourceForge.net, use, reproduction, modification, and other intellectual property rights to data stored in CVS or as a file release and posted by any user on SourceForge.net ("Source Code") shall be subject to the OSI-approved license applicable to such Source Code, or to such other licensing arrangements as may be approved by SourceForge.net as applicable to such Source Code."

    But, alas, I'm not going to get into a p***ing match with you, or anyone, over this. And I never once stated I would not show anyone the source. The only thing I stated is that it's not ready for public viewing (in so many words). :rolleyes:

    If anything take it up with SF and GPL. I'm sure they have so much time to worry about my little program built in AutoIT. Have them remove it. I really don't care. I made this program to be useful to people, not to have to worry about this s***, "oh I want the source Mommy! Why can't I have the source!?" Who are you Veruca Salt? Because, that's what it seems like to me. :wacko:

    But if you really want it THAT badly and THAT quickly you could always decompile it quite easily. :) Or you can just pm me your email address.

  4. You do realize that not everything on sourceforge has the code freely available. Nor is it in the contract to host programs on sourceforge. However, certain licensing terms to certain licenses do grant anyone access to source code of certain applications. It was never actually licensed properly btw. Meaning what I stated didn't make it licensed under any known licensing schema.

    I'm not saying I wouldn't be glad to offer it (besides finding the time to do so properly). But it's not written well and isn't commented at all.

    Besides my program is little more than a nice batch script for running RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers.

  5. That's because that's what your device path was before! If you do driverpacks twice it'll use whatever you had last. Plus, if you didn't have anything in there to begin with it'll add what you scanned as default. At least, that's what I think ;)

    So if you could test by changing that value to the default value and then run DriverPacks and see what happens that would be great!

    I think I have it setup so if you aren't using compressed drivers it'll keep the location of the drivers in the registry. However, as you've shown, it's probably better to always revert to the original.

    That'll be fixed in 4.5.2 :thumbup

  6. Okay just to get started the words slipstream and sata where unknown to me until yesterday. I have a dell i am working on with a western digital WD Caviar SE WD1600JD. I have tried several methods to uploading my sata driver but everytime windows promts for a floppy drive. I have tried the one on this site and i have tried nlite. Maybe i am just using the wrong driver? Is there a way to have windows, rather than sit there and wait for a floppy in A drive, allow me a dos promt? BIOS reads the HD fine and if i boot up without a CD, i get the start of windows followed by a dnsapi.dll error. I cannot load windows until i can upload that file from a bootable cd.

    Could someone tell me if i am using the right driver for my HD? western digital WD Caviar SE WD1600JD. I was trying to us fasttx2k. I am so frustrated right now. I seriously was up all night with 15 different cd's all with windows xp slipstream trying to get this to work. If anyone can send me the img i need and it works, i will send them 5$ paypal.

    Would i be able to have both HD's run in the same PC, and use one to read the other?

    Just use nLite to build it... www.nliteos.com

  7. but theres someway to know the drivers were correctly integrated without a true reinstall?

    I think they're injected into the wim image when it's created with vlite. During the deployment or installation it only uses the drivers it needs. I might be wrong though. You could always check for a dll that's in the drivers install on the new os install.

  8. hey there,

    does anybody knows some sure way to integrate nforce and geforce drivers in a Vista Ultimate x64 setup?

    I tried firegeier's and vLite method, but none of them seem to work... at least with vmware...

    any tips or solutions?

    tks

    Why would geforce and nforce drivers even load in Vista if it's running under VMWare?? It'll only load the drivers it needs.

  9. You can use nLite www.nliteos.com to slipstream drivers to a XP source and create a new cd from that source.

    Or you can get a whole bunch of drivers from www.driverpacks.net and have it's program slipstream it to the source. Then you'll need to make a new cd from that source.

  10. Hi,

    I wondered if anyone can help. I've just stumbled onto this tool and it looks quite handy. I have two questions, if this is the wrong post I apologise and if these questions have come up before please forgive me as I am a noobie:

    1. Does the tool (with the driverpacks) work under Windows 2000? The reason I ask is whenever I run the tool it doesn't seem to update / install any drivers.

    2. When I run the tool it extracts all the drivers and then demonstrates the follwoing error:

    "Error in Syssetup.dll"

    "Missing entry:UpdatePnpDeviceDrivers"

    Can anyone help? Thanks in advance

    It doesn't seem to work in 2000 in it's current state. I'm working on that. It does say in the notes that I've only tested it on XP.

    Are you looking for a resolution for the problem 'Continue anyway'?

    My life is busy. But I am working on it.

  11. I would really appreciate any help with this:

    I'm creating a HII and am having a heck of a time getting drivers to load. I would use the driverpacks, but the image size is an issue and can't include all of them.

    I'm building the image on a Dell Optiplex 755. The only driver I loaded was the AHCI SATA driver during the Windows install. All of the other devices were unrecognized and I left them that way. I made my changes to the image.

    I have all the drivers and have (manually) enumerated the DevicePath key in the registry - of course I found the Vernalex program after I did it by copying the paths into notepad. I was going to use the OemPnPDriversPath line, but unfortunately, in my org, the drivers HAVE to be on the D: drive - so I did the DevicePath key.

    I ran sysprep -mini -reseal. When the machine booted back up, nothing changed. All of the unrecognized devices were still unrecognized. BUT, if I told Device Manager to update the driver, it found the correct one automatically (thru the DevicePath key, I assume.

    Should I be running sysprep with the -pnp switch?

    I have already seen this post:

    http://www.msfn.org/board/Forcing-PnP-Enum...p;hl=devicepath

    Should I run that command (RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers) in a GUIRunOnce script?

    I'm baffled as to why the devices didn't auto detect during sysprep. They are all PnP - doesn't sysprep force a driver redetect? Or is that only with the -PnP switch? I thought the -PnP switch was only for nonPnP device detection?

    Thanks for any help!

    Sysprep must also be run with sysprep -bmsd before it's run with sysprep -mini -reseal. You also must specify all your mass storage drivers in the section SysprepMassStorage. You also must put in the Unattended section the below:

    [UnAttended]
    ...
    UpdateInstalledDrivers = Yes
    DriverSigningPolicy = Ignore

    This will tell Sysprep to update the drivers from the location(s) you told it in the registry key Devicepath. You are correct in assuming you don't use the parameter -pnp. IF all of your drivers are correctly enumerated and imported into the registry then Sysprep will install the drivers for you.

    But, I don't know if Sysprep just doesn't like that it's on a separate partition. I would try on root and the separate partition.

    Also, if you're using Vernalex's scanner don't let it search Windows\INF and see if that makes a difference. OR put it at the end of the line instead of the beginning in DevicePath.

  12. Is there something that clicks automatically on 'Start' to launch the install of drivers?

    Yes in the INI file you can edit the Automatic_Install to Y under the section AutoInstall.

    So basically get your settings all the way you want it via the gui and then click on the Menu "INI File" > "Save INI" then "Edit INI". Edit it the way I said and then save and close the INI file (which opened in your text editor). Close out of DriverForge and the next time you run it it will install everything with the settings you chose automatically.

    Stupid question from me, I did the change already

    HWPNP and Devcon doesn't work for me so it's using the windows native mode and there I sometimes have to click 'Continue Anyway' when the driver isn't signed. :wacko:

    picpostdriversvp3.jpg

    Ahh... There's a program that should be running to turn that off. I guess it didn't. I'll see about that in the next version! Thanks for the update!

  13. Is there something that clicks automatically on 'Start' to launch the install of drivers?

    Yes in the INI file you can edit the Automatic_Install to Y under the section AutoInstall.

    So basically get your settings all the way you want it via the gui and then click on the Menu "INI File" > "Save INI" then "Edit INI". Edit it the way I said and then save and close the INI file (which opened in your text editor). Close out of DriverForge and the next time you run it it will install everything with the settings you chose automatically.

  14. That's great Kenedy! Perhaps yours will also work with PE?

    I was actually about to integrate DPInst.exe into my program as well. I have devcon, windows native and HWPNP already.

    I especially like your copy function though. Very useful.

    Zjokes, it might not work with Dutch because he might have used only the English-US version of the file. The US version is only around 500k and Localized is almost 3000k.

×
×
  • Create New...