Jump to content

Endo

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

Everything posted by Endo

  1. Not sure if this has been mentioned.. But multiple Start Before/after's would be good
  2. Or use AUTOIT to do it in XP.... ; ---------------------------------------------------------------------------- ; Set up our defaults ; ---------------------------------------------------------------------------- ;AutoItSetOption("MustDeclareVars", 1) ;AutoItSetOption("MouseCoordMode", 0) ;AutoItSetOption("PixelCoordMode", 0) ;AutoItSetOption("RunErrorsFatal", 0) AutoItSetOption("TrayIconDebug", 1) AutoItSetOption("WinTitleMatchMode", 4) ; ---------------------------------------------------------------------------- ; Script Start ; ---------------------------------------------------------------------------- BlockInput(1) Run("rundll32.exe shell32.dll,Control_RunDLL appwiz.cpl,,2") WinWaitActive("Windows Components Wizard") Sleep("4000") WinActivate("Windows Components Wizard") Send("!C") Send("internet") Send("{down}") Send("{space}") Send("!N") WinWaitActive("Windows Components Wizard","Completing the") Send("{enter}") WinActivate("Add or Remove Programs") Send("!{f4}") BlockInput(0)
  3. Does anyone know if there is an easy way to detect if a machine was: 1) Rebooted and Logged on (shutdown or reboot state?) 2) Logged off and logged back into without being reboot/shutdown I cant use Vbscript, if its doable in kix32 then its all good The reason for this is im trying to establish if there is a bug in windows... We run Terminal servers with citrix yadda yadda.... In our login scripts we have a check for the Clientname variable which is only supposed to be set when you are logged on to a Terminal session. What I am finding, and I would like to add a check in the logon scripts to get a bigger picture, is that when you first logon after a reboot or shutdown the CLIENTNAME environment variable equals console... Kinda annoying. Thanks
  4. Not sure if anyone has shared this, but it worked for me so hopefully it will work for others... One of the most annoying things is the lack of bluetooth functionality within 2003... It really p***ed me off, and i know it must annoy others so I hope this works for others. First off you need: A machine with Microsoft Windows XP Sp2 Your 2k3 machine needs Sp1 Both machines networked. This trick may be familiar to people who use a systems driver cache to reinstall drivers... First off, go through the install process on the XP machine. This will setup the bluetooth stack and everything else.. once you get it all up and running: 1. Map a drive to your xp machines admin$ share. EG Net use X: \\xp\admin$ 2. Insert the bluetooth receiver into a usb port on your 2k3 box 3. When prompted, choose to install the driver manually 4. Point the driver install to X:\INF This will kick off the install... Windows will prompt you to install different files, there are a combination of locations that you use to do this: x:\system32 x:\system32\drivers x:\driver cache\i386 (The SP2.CAB file is located here, you might need to extract some files from it) c:\windows\system32\drivers There is also a chance you will get an error regarding irprops.cpl, this is the bluetooth control panel applet. you can find it on x:\system32. There are a couple of notes: My system did not detect the mouse with the proper description as pointed out in the manual when i did a bluetooth scan... For some reason... my mouse is called "stevie" The other thing is that intellisync will NOT have the bluetooth mouse listed, i used the Wireless Intellimouse explorer 2.0 setting and it all works fine. The wireless receiver does pick up other devices like my phone.... now if i can get the pcssuite to work i will be happy
×
×
  • Create New...