Jump to content

pSycho-Y2K

Member
 View Profile  See their activity

  • Posts

    44

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    Netherlands

 Content Type 

Posts posted by pSycho-Y2K

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    No, I don't have a similar window as you described, just the standard Found New Hardware window where you have to press Next to search for a driver. But I wrote a small VBS as a temporary workaround until this is resolved. :)

    Dim WshShell, DriverTool
    Set WshShell = WScript.CreateObject("WScript.Shell")
    Set DriverTool = WshShell.Exec("Hardware.exe")
    Do While DriverTool.Status = 0
    WScript.Sleep(5000)
    WshShell.SendKeys ("%+O")
    Loop
    WScript.Quit

    The code waits every 5 seconds to press on ALT+O which is the keyboard action to press Next in the dutch version, it loops until the program is finished. That way, the problem is solved as a temporary fix. I still don't know why only the Finish button works. I'm very happy knowing the installation-disc is now fully unattended :D

    0

    nLite 1.4.9.1 - Honey Turbo 9.1

    in nLite

    Posted

    Nuhi, I really like your tool :thumbup

    I don't know if this already has been discussed, but is there a way to Disable Driver Signing as a tweak?

    Currently I use a VBS script to automaticly go to sysdm.cpl and pushing the buttons to disable it (with sleep commands to wait for the windows to pop up). But unfortunately on slow or heavy loaded systems it doens't work properly :(

    Maybe if you have the time, you can add this to nLite?

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    I've made some succesfull progress tracing the "COM Error with DOM!" 80041013 error. It seems related to the removal of the "Help and Support" component in nLite. Leaving the component alone did the trick :thumbup

    I'm still trying to figure out my previous problem with the dutch version of the Found New Hardware Wizard where it doesn't repond to Next, but fortunately it does work with the Finish button :blink: I'll try to mess around a bit more with the settings. Madboy, maybe you can see where the problem is? See my previous post for the log and settings.

    Another thing I'm struggling with is the Driver Signing policy. I let nLite disable the Driver Signing Policy, but unfortunately it switches back on during the first boot after a fresh Windows installation. Hacking into the registry doesn't work as Windows recognizes the action als a harmfull attack. My workaround for this is a VBS script which automaticly go to sysdm.cpl and pushing the buttons to disable it (with sleep commands to wait for the windows to pop up). Then your tool will be executed and the drivers will be installed without unsigned driverpopups. But unfortunately, on slow or heavy loaded systems it doens't work properly :(

    Maybe if you have the time, you can add this also to the drivertool?

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    Okay, I did another run with the program with debug logging activated. I think the first error relates to nLite where I've deleted a few components. With a fresh installation (with an original Windows XP) the error doesn't appear. So unfortunately I have to pinpoint the specific component.

    I see a lot of information like you said in the advanced tab, lots of specific hardware components and values. I guess this part works as it should be. And it also detects the window title of the Found New Hardware Wizard and the Finish button.

    I've added the debug log to this post, I hope this helps :sneaky: PS. All tests are done in VMware Workstation

    hardware_installer.txt

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    Nice to see some progress in your software Madboy! :) I tested version 2.0.0.20 yesterday, and it seems that I still have some (minor) problems. The first one is an old one which I still can't get rid off. The program starts normally, but when it's "discovering advanced information about all system devices" an error pops up where I have to click OK to let the program continue (see screenshot). After clicking, it's runs just fine and the drivers will be installed, pretty strange :wacko:

    The other problem relates to the Found New Hardware Wizard. With version 2.0.0.20 it does half the job with the dutch language: A driver wizard still pops up where I need to click Next (which is Volgende in dutch), the tool doesn't do anything here to click the button. When pressing the button manually the system searches the driver and installs the driver from the DriverPacks folder.

    After that, the wizard prompts us to click Finish to close the wizard. Fortunately your tool presses the Finish button (which is Voltooien in dutch) correctly and the wizard closes. So only the Next button has to be pressed manually. :(

    I've added the log, config and screenshot to this post.

    post-34235-1203249396_thumb.png

    Hardware_config.xml

    hardware.txt

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted

    Ahh wonderfull! :D But unfortunately (I sound like a whiner now :P) the Found New Hardware Wizard still pops up and the user has to press the Next button manually. I doublechecked the XML script but I don't think there's anything wrong with it:

    <hardware_wizard>
       <wizard_use>Yes</wizard_use>
       <wizard_title>Wizard Nieuwe hardware gevonden</wizard_title>
       <wizard_button_cancel>Annuleren</wizard_button_cancel>
       <wizard_button_next>Volgende</wizard_button_next>
       <wizard_button_finish>Voltooien</wizard_button_finish>
    </hardware_wizard>

    As you can see, I'm using the dutch version and the title and button labels are correctly typed (see screenshot). Maybe another bug? :) PS. Good job on the fast bugfixing! :thumbup I'm looking forward to see the program working fully functional.

    post-34235-1200658765_thumb.png

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    I have just found out that some chars can't be properly used in .xml file. For example i tried to use some french apostrophes in window name and it wouldn't let me. So i have to find another way to store the information that is required for Window managing. Unless noone is using other language then English ...

    I'm using the Dutch version, and we don't use apostrophes in our language. But unfortunately the latest version of the tool generates the following error: Method must be set: SetupCopyOemInf or RegistryDevicePath. Terminating! In the logwindow I see the following line: [16:37:48] - [CONFIGURATION] Wrong settings for Plug And Play Option. Setting method to INTERNAL.

    I used the new default configuration supplied in the zip, and altering the requested values did not help :( Is this a bug?

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    I progressed a bit further and it's working properly now during the RunOnceEx process. The solution: msxml6.dll was not registered at that point. I've added regsvr32 /s msxml6.dll to the installationscript before executing the drivertool, and it's running perfect now :D

    The only annoying thing is the Found New Hardware Wizard which pops up occasionally. I'd like to suppress that Wizard, because it only requires Next and Finish when it's done. I know I can't disable it because it's a fundamental part of the hardware detection (it just doesn't do anything when you temporary rename %WINDIR%\system32\newdev.dll to something else). But as long as that thing is popping up, the unattended installation is never fully unattended. :( Maybe the drivertool can search for this Wizard window and silent pressing Next and Finish?

    post-34235-1198086057_thumb.png

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    The problem is with WMI so most likely you've corrupted WMI files or so. Maybe you removed it or somehow got it destroyed. Not sure how i can help you guys with this? Also have you tried the newest version or the one from first page. The newest version is somewhere in the last posts as i am too lazy to update the first post (and since i am preparing new version soon i don't see sense)!

    Okay, I'm trying different things now, changing nLite removed components and tweaks. Maybe there are some registrytweaks which cause the problem, so I'm going to fiddle around some more these days and hope to solve the issue. :)

    Update: I see some progress now, it seems an application is disorting WMI. I temporary removed the installation of applications, and it seems the program runs perfectly now :D I'm going to test some more.

    Can you explain exactly what you have in mind?

    Let me rephrase the question: Plug 'n Play has two options Internal and Devcon, what does it do and what are the differences between them? When should you use the Internal (default) and when Devcon?

    0

    Drivers Instalation in Post-Install stage (New Method)

    in Device Drivers

    Posted · Edited by pSycho-Y2K

    It seems that the 800401F3 problem has also plagued me. I tried the solution earlier in the thread by using RegSvr32 to register DLL and EXE-files. But it didn't help, not even after a reboot. I think it has to do with nLite which removes and de-registers certain files from the installation, but I don't know which component or setting is responsible for this error. I attached a screenshot of my installation-dvd where the error is displayed. I used the RunOnceEx process to install applications and the automatic removal and installation of the device drivers by your program. Maybe anyone can pin-point the problem for this? :unsure: I'm using Microsoft Windows XP SP2 (US) VLK with all recent hotfixes/updates, and IE7 & WMP11 slipstreamed.

    Funny thing is that while testing and trying out some settings, the drivertool did actually work! I just can't put my finger on it... :wacko:

    PS. I love your work! It's really the cherry on the cake for a complete unattended installation! Maybe you can tell me what Devcon does compared with the default value?

    post-34235-1197894873_thumb.png

    0

    Luna Royale and Vistaluna

    in XPize

    Posted

    Note: I've originally posted the following in the XPize v4.6 Beta 1 topic, but I think it's better here:

    I have a problem in the Luna Royale theme that's bundled with the XPize v4.6 Beta 1 release. When you view a thumbnail in the My Task Panes (i.e. My Documents) the picture shifts to the right and it looks a bit weird :blink: Another problem is that the White color is displaying as an alpha channel, and since these Task Panes are gray; photo's and other pictures with white in them look distorted. :no:

    I'm currently not at home and I can't post pics just yet, but it's fairly easy to reproduce as I described.

    0

    [Release] XPize 4.6 Beta 1

    in XPize

    Posted · Edited by pSycho-Y2K

    I have a problem in this release, when you view a thumbnail in the My Task Panes (i.e. My Documents) the picture shifts to the right and it looks a bit weird :blink: Another problem is that the White color is displaying as an alpha channel, and since these Task Panes are gray; photo's and other pictures with white in them look disorted. :}

    0

    XPize 4 MCE BETA 1

    in XPize

    Posted · Edited by pSycho-Y2K

    @boenki:

    Never had the bmp issue. If someone else has experienced that, please report. About the text of the installer, thats no problem.

    I've got the same problem, I have 3 bmp errors right after each other when all the 3 Royale themes are installed.

    But, I probably think it's an error by nLite where you can change certain Windows variables, I guess your installer is searching for default values which have been modified by nLite.

    For now, I haven't found any other problems so far. Still testing though! :D

    0
×
×
  • Create New...