Jump to content

nervster

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Romania

About nervster

nervster's Achievements

0

Reputation

  1. I've been trying to install Windows XP using different USB sticks for the last two days. I encountered different issues while doing so, but I managed to fix everything, except a few. I'm using nLite and Bashrat's DPB. nLite is used to remove unneeded components, slipstream some patches and for unattended purposes (that's what I'm using it for). The problem is, I can't get the contents of the $OEM$ folders to copy to %systemdrive%. I can't understand why do I have to remove the [unattended] section from the *.sif files, although I understand that the installation will still be unattended. Anyway, I've removed the [unattended] section from usb_multiboot2\winnt(_bf).sif and from \I386\winnt.sif. I'm not quite sure if one has to remove it from all the 3 winnt.SIF's, maybe just the ones provided by usb_multiboot2. Although the "$$, $1, etc." folders don't get copied to the %systemdrive%, cmdlines.txt is executed at T-12. Everything works (drivers installed) just fine if I'm using the regular method (CD/VM). This implies that the [unattended] section needs to be kept in \I386\winnt.sif. I've tried VirtualBox/VMWare/Virtual PC, but none of them seem to support booting from USB devices. Correct me if I'm wrong, please! EDIT: In the meantime, I came across this. I now understand that it wasn't me doing something wrong (besides not thinking of an alternative). Thanks for your time.
  2. OuttaSight's ".cfg" file is so f***able. You take the time to add every app that you'd like to be autohidden, save and exit. Then, as soon as you click the "AutoHide" tab, you'll be able to see the last added app multiplied by the number of added apps (the ".cfg" file doesn't remember every single app you've added, instead it populates the list with your latest added app). This hasn't got much to do with AutoIT, I know, but if one is using AutoIT on his unattended CD, maybe he'd also like to see no dialogs/windows. Some installers support switches, some don't, that's when AutoIT comes in.
  3. I can't recall, I gave up scripting .au3's when I found OuttaSight. You'd have to point WinExists/WinSetState to every window that opens up, which would take some time to script. While using OuttaSight, the whole process is a lot easier. Maybe it works for you.
  4. I have tried every possible way to achieve this (hiding any window/dialog without pressing any key). I've even tried WinSetState(), WinSetTrans(), WinMove() without any successful result. But then I came across Outtasight (which can be found here), which seemed to be working, but just for a while. All you have to do is to add the name (not path) of the executable that you want to autohide and you can add as many as you like. The down side is that the config file (which should've kept track of those added executables) goes crazy after you reopen Outtasight. I've googled, I've searched every forum that I came across but without a result. I hope there's someone out there that can help me and everyone else who'd like to try AutoIT+Outtasight. Thanks.
×
×
  • Create New...