topdog

Hope it works - I'd only heard second hand from someone else who used it for the same scenario you're getting, but in my own case I was getting BSODs unplugging the X52 (randomly) or my PC going into limbo/crash state when trying to shut it down until I made this change, and it's been good as gold since. Never had it prevent me from booting up that I can recall; but I do have a device that does (and a very odd one at that) - an android phone when I have it connected via USB just causes my PC to hang in both the BIOS screen and during startup.

How come? If you don't intend maintaining a history/library of multiple backups, the least you can do is offer some protection to the one you're counting on. It's not necessarily the most cost effective strategy, but it is a strategy if you value time and effort > money. Just wondering if that's your only objection or you have some other consideration in mind.

Locate the Saitek DirectOutput service and change the startup method to Delayed.

:music_whistling: but he is done testing this sorry issue for a while! :lol: I know.. I should have known better, I know how I'd be in the same situation.

You should get 'the bump' when you press trim in a number of aspects and manouvers, from having by that action just neutralised and started afresh the influence over the control surfaces applied by the autopilot dampers (no longer holding you back from the course you've set with the cyclic, where you were essentially 'fighting' against the AP to set your current course). It seems natural enough, even if footage of it is scarce.

... as I still believe in many circumstances, you should :)

Notepad++ is preferred due to some multi-byte character encoding used in the files, though in this case I used Crimson Editor because it was closer to hand and I could see nothing that I'd be screwing up in this particular file by using it (I wouldn't recommend it for any files where cyrillic characters are used as part of the data itself). http://notepad-plus-plus.org/ Both are free (as in beer).

What about this? Insertions highlighted in blue against the original file (1 comment line added, and 1 original line changed). ------------------------------------------------------------------------------- function creatingINUFixPointState_onMouseDown(self, x, y, button) if button == 1 then --unselectAll() local lat, long = mapView:getMapPoint(x, y); if not isInMap(lat, long) then showWarningWindow(cdata.placeInside) return end local group; [color=blue][b]-- only helis have this callback anyway?![/b][/color] if base.panel_aircraft.window:isVisible() [color=blue][b]then -- [/b][/color]and (base.panel_aircraft.getView == 'helicopter') then group = base.panel_aircraft.vdata.group; else return; end; local x, y = mapView:convertRadiansToMeters(lat, long); pt = base.module_mission.insert_INUFixPoint(group, lat, long, alt, group.boss.boss.selectGroupColor, x, y) base.module_mission.update_group_map_objects(group) mapView:updateUserList(true) base.panel_fix_points.vdata.selectedPoint = pt; base.panel_fix_points.update(); return else panState:onMouseDown(x, y, button) end; end; ------------------------------------------------------------------------------- Seems like I can both edit (by dragging around) and adding INU points with this.

I was enjoying the campaign up until having to fly the apache.. I don't know, it just feels like I'm riding one of those bicycles where the handlbars have been pranked so when you turn them left, the wheel goes right. I'm hating it and its kinda stopping me from progressing.

Malwarebytes Anti-Malware is one of the products that failed to detect/remove the problem with the backdoor.tdss rootkit. I used the latest version of it at the time, and it offered no protection (note: this was in the last 2-3 weeks).

http://slideshow.techworld.com/3253342/best-video-games-and-gadgets-of-christmas-2010/10/ Got directed to this page whilst looking for news about stock levels in the UK for a logitech g27 wheel of all things, and couldn't help but notice in early slides following in from the opening screens covering Blizzard and the new WoW expansion a mention of DCS A10C and the TM Warthog. It's only a small pic and text, but nice to see it receive some coverage in what's titled "Best video games and gadgets of 2010". Click on the slide-out tab beside the pics for the accompanying texts.

If you had gone NVidia though, you'd need 2 cards to have outputs to drive 3 monitors and be without Eyefinity (which, as much as I'm generally anti-ATI, has seemed to be a good thing). Can be done, but all in all it seems to me that ATI (I mean AMD..) has an edge on the multi-monitor setups currently.

Saitek can be very hit and miss, so as tempted as I was to wait for and get them, I went for 'tried and trusted' (or at least, 'tried and known') existing availability pedals instead. So I recently (about a week ago) got the regular Saitek pro flight rudder pedals, which are going to be around half the price of the combat pro ones. I'm maintaining a couple of PCs at once anyway so if the new ones become a 'must-have' item, I can retire off these pedals to accompany the now-neglected X52, but probably not for at least 6 months. That was going what was going through my mind at the time of purchase anyway, and now they've arrived, I might just extend the period for retirement to 18+ months (depending on how well these ones last). They're good enough so long as quality doesn't noticably deteriorate over time. Actually turns out to be a good decision for me, as I'm a bit of a noob at pedal rudder controls it seems. I had ch pro pedals like 15-18 years ago - their current ones incidentally look no different other than for change from gameport to USB - but since then only used twist-stick style rudders, which of course I don't have anymore on a device like the TM warthog. I don't think I'd appreciate the difference between these pedals and 'better' ones anyway for a while. Programming 3 axis and 0 buttons isn't really much of an issue, only reason you'd want to use any programming is to tweak deadzones (hopefully none needed though) or curves, rather than macro programming. I'm not bothering with any software at the moment. I'm also saying all that, with the expectation that from a software perspective, the new combat pedals are going to be identical. What looks to be different about them is design and materials for the hardware and not their functions (though I'd hope for improvements in quality/precision and not just aesthetics for the price hike).

They have more difficulty in getting 're-installed with zero effort / code of their own' when SRS is off, is all. It's just one of those features that Microsoft put in with good intentions (if by good, we mean, reducing bad PR and burdens on their Support department, by making the OS more self-healing), that is all too easily exploited because it is too transparent and unconfigurable to us users/administrators as to exactly what it is doing and when. Just like hooking into and leeching off other Windows elements, like the graphics subsystem, is a 'good' method at letting legitimate and clean code end up serving an illegitimate purpose. So again though, disabling SRS is just a part of the process, and I would not rest there. You've gotten a golden warning about being compromised by probably only the 'weakest link' in a virus package, and it should serve only one purpose: to cause you to seek out and purge the rest. Hopefully it will be for nothing and you will have been lucky to only get the lone keylogger, but we already know you're not that lucky to just chance it being so without the extra diligence, since your system has already been proven to be successfully compromised recently. The family I had to get rid of recently included ALL of the following in ONE payload: - Modified MBR backdoor - Graphics subsystem hacked - SRS manipulated - Data-stealing background web agent - Keylogger - Ransomware 'cure' offerings posing as Microsoft partner products - Several random-name random-key backdoor Service installations (note: they don't show up in Device Manager or the Services applet, only in the registry) - Firewall disabling - Auto-updates disabling / DNS hijack (instead, converts things like Windows Updates into another re-installing backdoor) - Background banner-ad clicker botnet slave (note: again no browser apps/processes running, this is how some of the criminals are funding their illegal activities, by siphoning money from clean businesses just trying to advertise their products online) The only clue this was happening could be seen by an occasional/rare flicker of the screen (like a change of resolution just happened) or by mercilessly monitoring and confirming all IP traffic (actually checking each packet stream to see where it was going and what it was carrying, not relying on strict firewall rules). Some of these I cleaned by hand, some I could not, but this was all from just one source (aka Win32/Alureon or backdoor.tdss), and was able to run in the background still after the hand-cleaning, whilst there were 2 anti-malware product agents that were 'protecting' my system and a 3rd was running on-demand to scan and find the threats. All 3 were failures (but not all would normally expected to be). The entire machine was quarantined during this time so I had no concern about it actually doing any harm with the above (after I watched the network traffic in Wireshark, I had already advised my router to dump all network traffic from that machine to a bogus internal IP, so I could continue to monitor it and the success of the apps trying to deal with it), otherwise it would have been tempting to just say purge and burn the disk, and do a reinstall of the OS. I hadn't had to deal with a good infection for some time though, so I wanted to persist just to bring me back up to date on current affairs of malware. If you're content with your level of diligence, fine, I won't press it any further (or beat a dead horse) from here on. I've made my point, and based on what you've posted, I would in no way make any assumption that the system is clean - I could only conclude that one unsubtle threat was cleaned.

It looks like there's some intention to make it software controllable, but the current software doesn't have the capability in it yet to drive this feature. @Loz, I hope you've gotten some reply in the last day or two? It is quite bad to not be getting any non-automated acknowledgement from a customer service department (even at this time of year). If he's still not getting any response, is there anyone here with contacts into TM who would be willing to pass on the concerns over not getting supported for problems caused by the hardware/software?

Good find, but I would not rest there. It's quite likely you've disabled only 15-20% of the infection. What you have there appears to be a keylogger, but the drivers tampering may well have been embedded in, (the item in HKLM\...\CurrentVersion\Run disabled through msconfig wasn't amongst any driver files itself,) and generally these items don't work alone. http://www.microsoft.com/security/sir/story/default.aspx#section_3_1 These botnet 'families' often deliver a multitude of threats at once and some are more discrete than others, and can continue to operate in isolation. You may not be recording and sending keypresses to a botnet anymore, but you may still be doing other work for them. Until a recent encounter with a particularly sneaky one (thwarted attempts from a good quantity of anti-malware products to find or eradicate it, similar as to your own experience), I wouldn't have given a second glance at the product that did cure it, now I would use it in the first instance if I saw anything similar, and I recommend you do the following: 1. Turn off System Restore service (this allows Windows built-in file protection method to keep restoring malware that has taken advantage of it, you need to do this until the system is certain to be clean again). In Vista, right-click My Computer -> Advanced System Settings -> System Protection -> uncheck disks. 2. Download (possibly to another machine then copy across with usb key / cd) the latest Dr.Web CureIt! file from http://www.freedrweb.com/download+cureit/ 3. Boot up your machine into Safe Mode (which isn't safe, but does reduce the number of necessary running processes on startup which helps). 4. Run (no need to install) the CureIt! file and use its Enhanceed Protection Mode (acts like a 'secure shell', like Windows admin prompt screens, and disables interaction from many sources). 5. Once it completes, you can delete the file from your computer again (anytime you need it, grab the newest version anyway, don't rely on an old copy), and re-enable System Restore. If you were hit by any of the Alureon / Koobface / etc. variants that have been resurfacing with new and potent deliveries over the past couple of months (even though the botnet families themselves are years old), you're going to want to do a more thorough search for rootkits, tampered MBRs, tampered system drivers, etc. These have been successful in getting past some 'up to date' patched systems running anti-malware products on them, and do a nasty amount of data/identity theft. For example, I've watched one trying to reach what looks like a 'legit' website with a 'bad' URL that generates 404 responses, so what looks like a harmless virus is in fact sending via cookie and URL querystrings a constant dribble-feed of personal data from your system to their own. Without any 'browser' software/processes running, without any random executables running, as it had just piggybacked onto the Windows graphics engine via gdiplus.dll and was able to be triggered by anything that any app was doing to redraw a window frame (it may have clinched onto the Close button, or the alt-space application menu, or anything, allowing it to remain well hidden and frequently accessed/launched by oblivious user actions through non-infected apps). If you did somehow only manage to contract a single infection, you may have gotten lucky by just being a standalone keylogger used by some of the MMO game account stealing attacks (whether you even play them), but I wouldn't take the risk, and I also wouldn't count on what even 1, or 2, or 3 different anti-malware products reported, I've seen more than this fail to detect/cure a modern threat variant until a month+ after it has been into the wild.

Can't fathom why there'd be an app for 370KB of code that could be done with just a web page (that could be saved locally to the android's sdcard). It doesn't do anything except edit/display the list right? Not knocking the checklist itself :) Just I wonder what goes on in some developer's heads sometimes :)

Right... the yellow stuff was there before the new software and firmware patch, it's still there after, and it's still what you use (and see in Device Manager, since these are the connected devices and DM doesn't show what isn't connected). The red stuff is newly installed by the new software, but it's only seen and connected momentarily, then disconnected again, so you'll never really see it in use, even though these are the devices that carry the new names. They didn't exist before applying this software update. And hence, if there are problems, why it might be an idea to run this software so you can see what's what. Note I'm sorted on Vendor ID to make it easier to group them up.

They don't show in Device Manager as joystick/throttle because those devices are 'disconnected' except during the patching of the firmware. So they are installed under those names and IDs, but still registered as the previous 402 / 404 hardware device IDs (hid usb) that they were pre-patch when you plug them in and Device Manager picks them up.

After the firmware update, USBDeview still shows my stick and throttle connected under 402 / 404 devices, but the joystick bulk shows up as new device 401, and the throttle bulk as device 403. Neither of them show connections when reconnecting the devices, seems they were only needed and used during the update/firmware process itself. The details for installing both looked to be held in the same driver information file too (oem30.inf for me, but it may be a different value for you, and coincidentally oem28.inf and oem29.inf were the files I had for the original installation of the stick and throttle out of the box). P.s. Did you see my earlier reply, about 1 hr 20 mins before this one?

Meh, had a post typed out then lost it. @Loz, foremost I'm sorry to hear of your problems :( You mention the devices being recognised as *something* when you plug them in, which might be promising. I take it you don't have another PC you can try it on (which wouldn't even have the bulk whatsit that seems to be new) to see if it can be recognised like before? If so, it would seem to be some incompatible or failed software driver install that can hopefully be resolved (and if that is the case, I would first try unplugging both devices, rolling back to a restore point earlier than the firmware update, reboot, then plug back in to different USB slots than you've been trying, to try and force it to refresh). You get the typical Windows "bing-bong" noise for both of the devices as you disconnect and reconnect them still right? You could also run this and look for the devices that have Vendor ID of 44F (which is Thrustmaster) to see what it's saying about the list of devices, and what it thinks each one is linked to via the Connected yes/no column as you plug in / remove each one: http://www.nirsoft.net/utils/usb_devices_view.html (Incidentally, before the firmware updates, they do just show as standard USB HID devices and if it wasn't for the Vendor / Product ID you'd not be able to tell it apart from a $3 Microsoft mouse in the list). My product ID's (for USBDeview or scavenging around the registry) pre-flashing are 402 for the stick, and 404 for the throttle. I'll be giving the firmware update a go soon but currently just scouring my system for anything TM related and taking copies/notes of it first.

http://ts.thrustmaster.com/eng/index.php?pg=view_files&gid=1&fid=3&pid=311&cid=1 I haven't tried this - frankly because I'm not sure why I should, but FYI.. If anyone digs up a real changelog for it (other than it just pushing the firmware versions up) it would be good to share that too. It might be inside the download itself perhaps, haven't checked yet. All it says on the link above: Changes : Includes Firmware versions 10 (Joystick) & 18 (Throttle) Protection of the flash write through HID to avoid potential flash corruption

You know that the warthog is a little odd and that sometimes you might think a button is off/depressed, when actually it is on? For example, closing the throttle down completely to the 'engine off' position is actually pressing ON a joystick button for each one. To get the desired result, you actually need to put them into the engine idle position instead. Flaps should be on MVR, and other switches should either be centered if they have a center, or down if they're only 2 way. Center the 'fakey' throttle friction wheel. In this way, you should find in the Windows Control Panel > Game Controllers > stick/throttle that all the buttons are off, and it should stop appearing to auto-assign itself to any input configuration software.

Haven't played with it too much to get a feel for it, but I had noticed sometimes I have this problem and seem to be a few degrees adrift (and need to kick the pedals a little to swing the aiming reticle over the target before firing) and sometimes I don't. Someone explained in another thread that the autopilot/trim was having an influence over the turn to target positioning (under certain settings perhaps). I haven't gone back to trying this out though.

I think I remember someone before having problems with turn to target, and when we got them to upload a track we found in that mission (or after a reinstall) they had the 'game mode' flight model options enabled. After turning those off (use the option to say 'use these settings in every mission' as well), it worked fine. Just something to check, or else, good to post your own track file of the problem so we can see what's going on and take control where needed. http://forums.eagle.ru/showthread.php?t=57921&highlight=turn+target