PDA

View Full Version : Girder, worked fine yesterday, nothing today...



Ron
October 13th, 2002, 12:55 PM
Sounds like a dead IRMAN to me. See what evation thinks.

Ron
October 13th, 2002, 12:55 PM
Have you ever tried hooking your irman up to a different computer, just to see if it works there ?

Ron
October 13th, 2002, 12:55 PM
Just disable COM2, and plug the IRman into Com1 :-)

Mark F
October 13th, 2002, 12:55 PM
WOW, that is weird.

Is there any chance the Com port(s) got disabled in the BIOS?

Since Girder AND IRServer don't work, I would suspect the hardware config. Either the port(s) or the IRMan or a cable/connector. Do you happen to have anything else that connects via serial connection (a mouse or ???) that you could try on the ports to rule them out?

Mark F
October 13th, 2002, 12:55 PM
I don't think IRMan would send data if it wasn't initialized.

The only concern I'd have about a USB->RS232 adapter is that IRMan is powered from the com port. I don't think this would be a problem since IRMan is receive only but the USB spec has a limit on current that can be drawn by a device.

I'm sorry I can't be more helpful. I understand how frustrating this can be. :(

avekevin
October 13th, 2002, 12:55 PM
I've turned my computer on this morning and IRMAN's working again :-?

I'll still see what Evation have to say, but i made no changes since last night :-?

Oh, at least it's working now, but for how long?

Dumb question, but have you checked the batteries in the remote?

Kevin

kev
October 13th, 2002, 12:55 PM
This morning when i booted my computer up, Girder was not responding to my remote commands, so i went into Girder and this message was displayed in the status bar

Error : Could not enable some of the input devices

I've tried changing the comp-port settings, tried com1,2 and 3 (modem is com 4), and tried changing the physical port it is connected to.

If i run IRSERVER (i'm using irman) it just displays no response for all com-ports.

I've tried rebooting the computer with no change.

It's soooo annoying seeing as it worked fine last night.

Anyone got any ideas?

Kev :(
Girder 3.1.2e, irman, windows 98 se.

Edit: BTW there are no conflicts reported in device manager...

kev
October 13th, 2002, 12:55 PM
I've not been in the BIOS, i'll check in a moment though.

Device Manager is reporting both com-ports are working okay thought.,

MS System Info reports
===============
COM-2 is using IRQ3 and COM-1 IRQ-4.

It is really irratating.

And before anyone asks, I only have girder OR irserver running not both.

irserver reports
==========
<COM1> no response
<COM2> no response
<COM4> Windows Denied Access (Modem)

Also, just before I reinstalled windows (on Wenesday) (it had become so unstable i had a max of 1 hours uptime) it stopped working, but was fine after the reinstall.

Is there anything to see if anything is being sent to the comports (for diagnostics), and would irman send any data if it's not been initilised?

If it is the comports, will IRMAN work on a Serial -> USB adaptor, and how would I configure it within windows 98 se?

kev
October 13th, 2002, 12:55 PM
I've just checked the Bios and the serial ports are enabled

If i select the Hollywood Plus as my device time, for the recived IR i get a string of E's, with one pair of EC moving through from left to right continusly :(

kev
October 13th, 2002, 12:55 PM
if i uncheck the "Skip UIR init check" i just get 585858585858 being contiusley being sent to Girder, it enables though... :(

kev
October 13th, 2002, 12:55 PM
ooooh, i'm now getting an error when starting irserver "Selected collating sequence not supported by the operating system" :(

kev
October 13th, 2002, 12:55 PM
Thanks, i'll get in touch with them.

kev
October 13th, 2002, 12:55 PM
Only the one machine to try it on unfortuantly, i've just sent a message to Evation asking for some advice.

kev
October 13th, 2002, 12:55 PM
I've turned my computer on this morning and IRMAN's working again :-?

I'll still see what Evation have to say, but i made no changes since last night :-?

Oh, at least it's working now, but for how long?

kev
October 13th, 2002, 12:55 PM
Yeah, checked the batteries.

All 3 remotes I use with Girder are not having any response and the cable one is still controlling the cable box.

It's not working again. :-?

kev
October 13th, 2002, 12:55 PM
I think i may have gotton to the bottom of the problem.

IRMAN is physically connected to COM-2.
However COM 1 is disabled (as it uses an IRQ my sound card requires). Whenever COM2 is recognised under Windows as COM-2 IRMAN is not working, but when Windows recognises it as COM-1 it works fine (and yes i do check Girder is set to the same port as windows thinks it is).

Does anyone know of a way to force COM2 to be regonised as COM1?

I'm hoping this is the problem as i still havn't heard from Evation.

Thanks for all the help so far, Kev.

kev
October 13th, 2002, 12:55 PM
I've swapped the IRQ's round in the Bios (my soundcard need 4, which COM2 was assigned) and enabled com-1 and so far all has been well - touch wood - i hope this has solved my problem....

kev
October 13th, 2002, 12:55 PM
Just to let you all know, i've recived a reply from Evation and they think it's probably faulty, and have offered to exchange it for me.

BTW, i didn't have IR Server installed, never mind running initally.

Icthus
October 13th, 2002, 12:55 PM
I also have an Irman. When I first set it up (with the software included on CD), it started out with the IRServer and an old version of Girder. When I upgraded to a newer version of Girder, the IRServer caused problems with Girder everytime I would reboot my computer.

I found that if I completely disconnected IRServer and set it to not start automatically with Windows, Girder worked fine. There seemed to be some conflict between the two, but all is working fine now. By the way, even when IRServer was running, if you go into Girder and File->Disable Input Device (F9), then File->Enable Input Device (F9) it would work until I rebooted my computer. However, with IRServer out of the picture, Girder functions perfectly.

Good luck.

Branton