 |
|
|
Can uICE work with my computer's / laptop's internal IR port? I get an error message about a missing oleacc.dll when starting uICE. What can I do? uICE suddenly shuts down without a message or causes Blue Screens (BSOD) when exiting. What's this? My trial version suddenly expired before the 30 days. What happened? My receiver device is not listed under Supported devices. Is there a way to use it anyway? Where can I get a supported receiver device? Is there a Windows 3.x version of uICE? Why no Windows 95/NT 4 support? What's the recommended way to control an application?
Can uICE work with my computer's / laptop's internal IR port? Can uICE work with IrDA? Internal IR ports are usually IrDA network interfaces. This technology was not designed to work with handheld remote controls, and most models do not work at all. Yes, IrDA is an infrared light based technology. But there are physical differences between IrDA infrared light and the light emitted by remote controls (wave length/frequency), and, even more important, remote controls and IrDA use protocols. These protocols are completely incompatible. Most IrDA receivers filter out all incoming signals that do not follow the IrDA protocol specification, so no matter how long you try, your hardware cannot work with remote controls. No, it doesn't make a difference whether it's a built-in, serial port or USB device. Because of all these troubles, uICE cannot and will not support IrDA. Very (very) few models seem to be able to receive infrared signals from RCs. If you're using Win98, read this. No chance under ME, 2k or XP.
I get an error message about a missing oleacc.dll when starting uICE. What can I do? This message usually appears on Windows 98 and NT4 systems
only.
uICE suddenly shuts down without
a message or causes Blue Screens (BSOD) when exiting. What's this? Simple solution: do not use patches, crackz or whatever
to "extend" the trial period. There are no working cracks around and,
since uICE uses several kernel mode components, they can even completely
crash your system!
My receiver device is not listed under Supported devices. Is there a way to use it anyway? If it is a serial port model, you have a fair chance.
Currently two different technologies are supported, the first talks to
the computer using the standard RS232 protocol (like a modem), the second
uses the carrier detect line to send raw signals (pulses and spaces). Additionally, if you have a BT8xx based TV tuner card
with internal remote control receiver, you can try to use the TV Capture
Board driver. Run the setup wizard for this device, then try to learn
some buttons. If it won't work, send the generated tvcard.log ( uICE\devices
folder ) to me and I will see whether I can add support for it. If nothing works, you have of course the option to send me a sample device for developing a driver. I can't help you without this since I can't do blind coding without hardware for testing, and I won't buy every device out there, sorry. Contact me if you would like to send me something.
Where can I get a supported receiver device? You can find some links to manufacturers and schematics for home-brew devices here.
I can't get my receiver device to work though it's listed under Supported devices. Am I doing something wrong? First of all make sure you have configured it. After selecting the appropriate device, switch to Hardware Setup and verify the settings. If everything is ok, click on Initialize and start learning buttons. Many remote controls are not hard-coded, so you need to learn in their buttons first before you can do anything.
Is there a Windows 3.x version of uICE? Nope. I have none and there will never be one, Windows 3.x is dead.
Why no Windows 95/NT 4 support? Come on, it's the 21st century. Even Microsoft doesn't support Win95 any more.
I have a LIRC/WinLIRC/DCD Line device
and uICE keeps telling me something about different signal lengths
or signals not identical, what can I do? Well, all these devices require software decoding of infrared signals. For this, accurate timing hardware is absolutely essential. The infrared light signals of remote controls consist of pulses and spaces (i.e. light on/light off) in the range of a few microseconds, and Windows is not a real time operating system. If your system is too slow, or your system hardware doesn't have timing circuits accurate enough to measure those short signal durations, you're out of luck. Even if you're able to successfully learn buttons, they may stop working if you're running CPU intensive applications, like DVD/DivX playback. So after all, I'd really recommend getting a device with hardware decoding support. Nowadays you can get one for almost the same as the costs for the LIRC device parts, so why bother soldering them together? Try eBay.
What's the recommended way to control an application? For the best performance, you should always try the PostMessage action first. With this one, you can simulate selecting menu items (also from context menus) or clicking buttons of other applications. Examine the included sample application presets, most of them make use of the PostMessage action. However, if you try to control a skinnable interface, you may experience problems with this action. Many of those interfaces are - in my opinion, sorry - quite poorly implemented, i.e. do not conform to the standard Windows architecture. If a special application function does not have an associated menu item or button, find out if hotkeys are available for this function. If so, you can use the Keystroke to application action, but I would recommend Keystroke to window, which requires less processing time. If neither of the above works, you can still use mouse actions to simulate exactly what you would do if you were sitting at your computer. This is of course a less convenient way to control an application, but should work in every case.
I'm trying to switch Media Player, WinTV or other applications into fullscreen mode with uICE, but everytime I press a button it goes to fullscreen and immediately back to windowed mode. What's going on? Some fullscreen applications detect if other windows come into foreground and switch themselves back to windowed mode. In this case, make sure you have all OSDs for this application disabled and General Options->Leave window focus after keystroke is checked. |
||||||||||||||
|
Copyright © 1999-2003 MediaTexX |
|||||||||||||||
Feature
Tour