$oIE = ObjCreate("InternetExplorer.Application.1")
If @error Then
MsgBox(0, "", "Error opening Internet Explorer: " & @error)
LogThis("IE Object Open Failed")
Exit
EndIf
$oIE.Visible = 1
$oIE.RegisterAsDropTarget = 1
$oIE.RegisterAsBrowser = 1
;steps to achieve reboot
;18 to advanced
;25 to Yes
;27 to reboot
Dim $routerAddress, $selectAdvanced, $selectReboot, $selectYes,$user,$pass
$user = "usernameGoesHere"
$pass = "passwordGoesHere"
$routerAddress = "http://192.168.1.1"
$selectAdvanced = "{TAB 18}{Enter}"
$selectYes = "{TAB 25}{Enter}"
$selectReboot = "{TAB 27}{Enter}"
$oIE.Navigate($routerAddress)
Sleep(5000)
Send($user & "{TAB}" & $pass & "{TAB}{ENTER}")
Sleep(5000)
Send($selectAdvanced)
Sleep(1000)
Send($selectYes)
Sleep(5000)
Send($selectReboot)
Sleep(5000)
Send($selectYes)
sleep(5000)
$oIE.Quit
$oIE = 0
One of the greatest tragedies of new technology is the ever growing problem of legacy technology. Software, hardware, middleware, operating systems… you name it. Especially as it relates to computer technology.
Unfortunately, the continual push to better/newer technology is that the old technology slowly slips into oblivion. Take Apple computer for instance… OS X is a fantastic advancement beyond OS 9. But, what if I’m happy with OS 9? What about an iPod, can you still use that generation 1 iPod with your fancy new Apple MacBook Pro? NO CAN DO!
This week, the challenge is Windows Server 2003. It’s old hat now. The new technology is Server 2008 R2. W2K3 is so old now that it will enter extended support by Microsoft on July 17, 2010. That lack of support by Microsoft also means that any new hardware that comes out after that date will not likely be supported by any vendor.
But forget about support in a few months. There are problems with driver support even now. Broadcom, a network technology vendor for many companies in the server hardware business, is now only providing a packaged driver setup for their hardware. It seems, even their technology has outgrown Windows Server 2003.
Don’t get me wrong, the problem I referring to here can be dealt with. Though it’s not simple, easy or fun, the problem can be solved. That said, it serves my point well. You can keep it alive for a while longer, but the returns are ever diminishing because of vanishing vendor support. It gets progressively more difficult to do simple tasks.
I believe that this is one reason that businesses have so much angst over technology. Vendors have taught them well that if they commit to a given technology, that there is no guarantee how long that technology will be around to depend on.
I’ll give you another great example of technology rot: Television. Have you been to the electronics store lately? Did you see even one CRT television anywhere in the store? Not likely. Everything is flat. Everything is HD. If you’re at all like me, you probably have 10+ year old television that your still making work because, there’s absolutely nothing wrong with it. It’s not your fault that the TV stations don’t broadcast in the format the TV came out of the box with. It’s not your fault that someone came along and decided that they were too good for a square size program.
Eventually, we all give into the new technology, not necessarily because it’s better, but sometimes mostly because the old version was made obsolete by something newer or fancier, but not necessarily better.
I see it from the vendor side too. I develop software. I know what it means to release a new version that fixes everything about the old version that you just hated or tweaks that one little thing that didn’t quite work right. As a provider of anything, you strive to make your product better every time you release it. As you improve your product, your' expertise moves to the new product and away from the old because that is where you now spend all your time.
So, what’s the answer to the problem? I do know that some companies are better at it than others (this takes the Windows vs Apple argument to a whole new level). My goal is to design everything I build to work with new features as much as possible while preserving what’s old. I don’t always succeed, but at least I’ve thought about it and worked hard to keep things working for everyone for as long as possible.
It never fails. Buy a new gadget and discover to your dismay that the practical implementation of the software that comes with said new toy, is not as good as the marketing people would have you believe.
In this case, we’re talking about the Logitech G940 H.O.T.A.S. joystick system. (HOTAS is Hands on Throttle and Stick, and in this case also includes rudder pedals).
So, I open up my new christmas present and discover that it works, but only partially. When trying to us the setup with a few older games, the rudder pedals didn’t work, instead, the Trim control for the rudder axis was being used instead. To make a potentially very long blog post short, here is the solution to that problem, at least in the case of Search and Rescue 4 and Vietnam MedEvac, and without having tested, bets are this will make Battlefield 1942 and several other games work as intended as well. The great irony is, that this can only be done by NOT using the provide Logitech device drivers for the G940, you have to use the generic HID game device drivers in order for this to work, because the Logitech drivers split the controllers into 3 separate devices, and that just makes this problem even worse.
After flipping through the Microsoft HID/joystick specs, and I found a way to reorder the inputs so that Vietnam MedEvac will work!
This is a registry hack, so, beware of the possible consequences. Never the less, windows allows you to override what control is assigned to a given input when used with DirectInput.
Steps for Windows 7 x64 (I haven't tried on XP, and I probably won't.
1.) Assign the generic HID/USB gameport device drivers to the G940. This makes it such that the G940 shows up as one device.
2.) open regedit.
3.) Search for G940
4.) you'll eventually come to the hive for HKEY_USERS\S-1-5-21-####-####\ System\CurrentControlSet\Control\ MediaProperties\PrivateProperties\Joystick\OEM\VID_046D&PDI_C287\
5.) Add a new key -> Axes
6.) Add new keys 0 through 6 (the key name is only a number 0,1,2,3,4,5,6)
7.) Add a binary value "Attributes" for each of the keys 0 thru 6
8.) Assign the value 01 81 00 00 01 00 30 00 the the attribute for 0
9.) Assign the value 01 81 00 00 01 00 31 00 the the attribute for 1
10.) Assign the value 01 81 00 00 01 00 32 00 the the attribute for 2
11.) Assign the value 01 81 00 00 01 00 33 00 the the attribute for 3
12.) Assign the value 01 81 00 00 01 00 34 00 the the attribute for 4
13.) Assign the value 01 81 00 00 01 00 35 00 the the attribute for 5
14.) Assign the value 01 81 00 00 01 00 36 00 the the attribute for 6
Now, this just keeps things as they are. So to swap the Z rotation axis, and the Z axis, we just need to swap the attribute assignment.
10.) Assign the value 01 81 00 00 01 00 35 00 the the attribute for 2
10.) Assign the value 01 81 00 00 01 00 32 00 the the attribute for 5
See what we did? Unplug the G940, wait a few seconds and plug it back in.
Go look at the properites in Game devices control panel now and see that Axis Z and Z rotation are swapped.
Similarly you could use this method for any of the axes that you want to change out.
Unfortunately, this only works when you don't use the Logitech drivers. But this also tells me that Logitech could easily fix this problem if they wanted to, all I had to do was take 30 minutes and read the WHDC documentation from Microsoft to move the axis assignments around.
Keep in mind however, that making this change could cause another game program to be mixed up on which axis goes where, but as I said, I have a suspicion that this will also fix the rudder pedals problem that I have with Battlefield 1942 as well.
