Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun.

As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Or read our to learn how to use this site.

Hi Bill and sorry for the delay. I was never notified you replied. Please do this. =================================================== Testing Computer Performance Using Ubuntu DVD -------------- For these steps you will need a blank DVD and download/create the disk from a clean computer if necessary.

Oct 22, 2011 - Fix the EAX Console installation error on Windows XP/Server2003. I'm thinking this?is becuase the driver does not support?win 7. Jan 31, 2016. But involve figuring out the place you're thinking that. Internet,Hotkeyapp.exe,Error 6003. To fix error code error, Dll Errors.

• Download onto your desktop. This is a large file so allow it some time to download • Insert a DVD into your CD/DVD player • Double click on the Ubuntu icon • Click Burn, then Close when completed • Restart your infected computer. Thank you for going through all of that Bill. Can you tell me if other computers or devices are attached to your router and working properly?

Please run this. =================================================== MBR Dump, Fix, and Scan Using Farbar's Recvovery Scan Tool in the Recovery Environment -------------------- For this step you will need a USB flash drive. • Press the windows key + r on your keyboard at the same time. Type in notepad and press Enter • Please copy and paste the contents of the below code box into the open notepad and save it on the flashdrive as fixlist.txt SaveMbr: Drive=0 • Please download and save it to a flash drive. You need to run the version compatible with your system.

If you are not sure which version applies to your system download both of them and try to run them. Zip Code Dma Mapping Linux more. Only one of them will run on your system, that will be the right version.

• Plug the flashdrive into the infected PC and follow the 2 step process below to enter the System Recovery Options using one of the three options listed, then running Farbar's Recover Scan Tool ---------- Entering into the System Recovery Options Option #1 To enter System Recovery Options in Windows 8: • If you are using Windows 8 consult to enter System Recovery Command prompt and skp the next two options. Option #2 To enter System Recovery Options from the Advanced Boot Options: • Restart the computer. • As soon as the BIOS is loaded begin tapping the F8 key until Advanced Boot Options appears.

• Use the arrow keys to select the Repair your computer menu item. • Select English as the keyboard language settings, and then click Next.

• Select the operating system you want to repair, and then click Next. • Select your user account and click Next. Option #3 To enter System Recovery Options by using Windows installation disc: • Insert the installation disc.

• Restart your computer. • If prompted, press any key to start Windows from the installation disc.

If your computer is not configured to start from a CD or DVD, check your BIOS settings. • Click Repair your computer. • Select English as the keyboard language settings, and then click Next. • Select the operating system you want to repair, and then click Next. • Select your user account and click Next ---------- Running Farbar's Recovery Scan Tool in System Recovery • Once you are in the System Recovery Options menu you will get the following options: Startup Repair System Restore Windows Complete PC Restore Windows Memory Diagnostic Tool Command Prompt • Select Command Prompt • In the command window type in Notepad and press Enter. • The notepad opens.

Under File menu select Open. • Select Computer and find your flash drive letter and close the notepad. • In the command window type e: frst (for x64 bit version type e: frst64) and press Enter • Note: Replace letter e with the drive letter of your flash drive. • When the tool opens click Yes to disclaimer. • Press Fix button. • It will create an mbrdump.txt file on your USB device. Attach that file to your reply • A fixlog.txt document will also be created on your USB drive.

Copy and paste the contents of that file in your reply • Under Whitelist uncheck the following items Services Drivers Processes KnownDlls • Click the Scan button • A FRST document will be saved to your USB device • Copy and paste (or attach if necessaery) the contents of that document your reply =================================================== Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it. • FRST log • Attached mbrdump.txt.

Greetings Bill, Thank you for the MBR report. I am afraid I must tell you of the bad news. =================================================== BACKDOOR WARNING! -------------------- One or more of the identified infections is a -.

This allows hackers to remotely control your computer, steal critical system information and download and execute files. I would counsel you to disconnect this PC from the Internet immediately.

If you do any banking or other financial transactions on the PC or if it should contain any other sensitive information, please get to a known clean computer and change all passwords where applicable. Please let me know if you have already noticed evidences of financial institution irregularities. Those accounts should be monitored from this point forward. Though the trojan has been identified and can be killed, because of it's backdoor functionality, your PC is very likely compromised and there is no way to be sure your computer can ever again be trusted. Many experts in the security community believe that once infected with this type of trojan, the best course of action would be a reformat and reinstall of the OS.

Please read these for more information: Here are some thoughts I have put together for people who ask what they should do in light of the infection. Ultimately each user must decide for themselves what to do and the below are things you might want to consider. It is necessary for us to at least make you aware of the worse case scenario.

This is because of the potential Backdoor Trojans bring with them, but it is not a determination on our part that your situation currently falls within this worse case scenario. Ultimately it is a personal decision whether to reformat or not. What decision should you make to let you sleep well at night? It is different for different people.

I will say whether rightly or wrongly most people decide to clean and not reformat, at least initially. The only insight I can offer is how I evaluate the issue personally even though I have never had a Backdoor Trojan on my computer. One of the primary purposes for malicious software is to somehow separate you from your money. It seems reasonable to assume that a thief trying to take your money via a Backdoor Trojan will hit you hard, and quickly. Once your computer starts to act up and you become suspicious you have the opportunity to eliminate access to your computer and change the information taken, namely account and password information.

The key to this, in my opinion, is whether or not you have noticed any irregularities in your banking or other financial institutions, or things like email and social network accounts (i.e. If you have not seen any evidence of that then you may question whether your information has truly been stolen. If it seems it hasn't, and your critical information has been changed, it is reasonable to be more confident you are safe but you must stop short of claiming an absolute guarantee.

If, after careful consideration you decide not to reformat your computer it would be wise to continue monitoring your sensitive data and don't wait to address future symptoms on your computer which seem to be malware related. The bottom line, the only way to be absolutely sure to be rid of a Backdoor Trojan is to reformat. The decision is yours. Oh My We can still clean this machine but I can't guarantee that it will be 100% secure afterwards.

Let me know what you decide to do. Gary, Have suspected as much since trying to resolve this issue in the last few weeks. The day after my computer started acting strangely, I changed all my online financial passwords. Had one email from a brokerage account that an attempt had been made to access my account but they did not have the correct security info. I also have been getting a lot of junk email after the incident. Fortunately, not on my gmail account. I will reformat and reinstall the OS.

Besides backing up the data files, what else do I need? Thanks again for all your time and expertise. I feel better at least identifying the issue.

If you've recently installed Informix Dynamic Server (IDS) 10.00.UC4 and have ODBC or other client applications, you might notice an error message like this when connecting to IDS: [Informix][Informix ODBC Driver] Database locale information mismatchThe problem is related to a an IDS bug fix in 10.00.xC4. The defect is: 171156 ABLE TO CONNECT TO DATABASE CREATED WITH UTF8 LOCALE WITH CLIENT WHEN DB_LOCALE SET TO EN_US.8859-1 Prior to this bug fix IDS would not complain if the DB_LOCALE environment variable was set to en_US.CP1252 on the client and set to EN_US.8859-1 or EN_US.819 on the database server.

This is a mis-match which is now correctly flagged as an error. The problem is the default DB_LOCALE value on Windows in the United States used to be set to en_US.CP1252, so if you didn't specify otherwise there would be a locale mismatch between the client and server by default.

The correct fix to this problem is to set the default DB_LOCALE value on the client to the same as the default value on the server. You can specify this in the ODBC connection string or when creating the. With IBM Informix Client Software Development Kit (CSDK) version 2.90.TC6 and higher the default United States DB_LOCALE is now set correctly and matches the server value. The related defects are: 175110 ICE: THE DEFAULT DB_LOCALE IN CREATING DSN'S ON WINDOWS SHOULD BE EN_US.819 and 175746 ICE: WHEN SETTING UP DSN, SHOULD GET THE DB_LOCALE FROM SERVER AND SET IT AS DEFAULT DB_LOCALE ON ENVIRONMENT TAB The latter fix makes it easier to set up a DSN without worrying about locales.

If you really need this working and cannot wait for a CSDK fix, and cannot change your application to specify a DB_LOCALE that matches the server in the connection string, you can set the IDS server environment variable IFMX_UNDOC_B168163 to 1 (ignore the fact that '168163' does not match any of the above defect numbers). The server will then revert to the old behavior of accepting the mismatched locales - however it is much better not to do this - mismatched locales, even when similar, can potentially lead to data corruption.[]. I was chatting about DBA skills recently (with a DBA no less) and the discussion drifted to the skills required by technical support engineers. Having spent the last 18 years in and around database and operating system technical support, here's my monologue on the subject. Many of these could be regarded as common sense and applied to other professions.

Note I don't claim to possess any of these skills. There's a lot to be said for making something up and hoping for the best. Top 10 Tech Support Skills 10. Subject and specialist skills. Expertise on the supported product is a given, but as often as nota problem occurs at the interface of a supported product and another component.

Hence aknowledge of all operating systems your product supports, all programming languages that clients can be written in, the networking layer used by your product, the assemblerlanguage it compiles to, are indispensable. In a tech support team if each person can specialize in one subset of the knowledge, that's a lot of specialist knowledge. This is good foreach engineer, though at an organizational enough shared knowledge needs to exist to survive any individual moving on in their career. Subject matter skills naturally extend to bug fixing and product development skills as you gain experience in a product. The appearance of memory.

Learning something, only to forget it when you need it 6 months later is a waste of time. Write down everything you learn and dump it ina Wiki or some other knowledge base for easy access. Search engine skills. Often the truth is out there and a tech support engineer just needs to be better at finding it. A knack for using the right search criteria can be all it takes. Generic problem solving skills. A good tech support engineer should be able to apply generic problem solving skills to troubleshoot any kind of problem, including for products they know nothing about.

Debugging skills. The ability to debug any code on any platform. Communication skills. A tech support engineer should be adept at sharing information with other engineers and customers, and building a network of technical contacts across departments, teams and other companies in order to get things done even when proceduresget in the way. Diplomatic skills. A support engineer needs to know how to diffuse high pressure situations by effective communication with all levels of management. What do you do ifsomeone is criticising your product and company, and you know they are right?

(Of course thiswould never happen with Informix.) A diplomatic tech support engineer knows how to listen well, and move the focus of the discussion to what can be done to improve thesituation - which ultimately is what everyone wants, even if they need to let off some steam first. This one sometimes gets overlooked. Many database tech support engineers go theirwhole careers without really understanding what DBAs do. If you want to help a DBA solve a problem you need to understand why the problem exists in the first place. Fanatical devotion to problem resolution. Problem resolution does not mean getting acustomer to agree to close a case, it means doing whatever it takes to understand and solve the problem. In some cases if there is a fundamental disconnect between what the product is designed to do and what someone wants it to do it can mean enhancing the product, or understanding the customer needs in a wider context and looking for other ways to solve the problem.

Commitment to destroying your job. As with any service industry a good tech support engineer knows that their ultimate goal is to make their job unnecessary - for example push for code development methodology that reduces bugs, work with QA to improve testing, work to improve documentation and customer access to knowledge bases, to the point where the need for a tech support engineer is obviated. This is of course an ideal, with the positive benefits of striving toward such a goal realized along the way. What did I miss? Comments welcome.[]. The dbaccess user interface might not have changed much since the invention of the abacusbut it's very flexible when it comes to running scripts.

For example to execute a file containing SQL commands against a database called mydb: dbaccess mydb sql_file.sql Or if the SQL commands already include a database connection statement: dbaccess - sql_file.sql If you wish to enter SQL statements interactively without the menu, enter dbaccess - - Suppose you want to integrate a series of SQL statements within a UNIX shell script or Windows batch file. A simple method would be to pipe commands one at a time into dbaccess, e.g.: echo select col1 from tab1 dbaccess mydb Or you could chain a series of SQL statements together to send to dbaccess. This is a typical methodwe'd use to create a self-contained bug reproduction. An engineer can then reproduce the problem byexecuting the shell script. Here's a UNIX shell script that creates a database, inserts data, queries a table, and drops thedatabase: #!/bin/shdbaccess.