Shop OBEX P1 Docs P2 Docs Learn Events
SX Key 3.0 still locks up on faster machines... — Parallax Forums

SX Key 3.0 still locks up on faster machines...

peterjpeterj Posts: 24
edited 2005-02-16 06:52 in General Discussion
I finally put the SX Key 3.0 software on my primary machine and it *still* locks up just the same way the 2.0 software did. Has anyone found a fix or workarround for this yet? Can we ever expect the SX Key software to fix this?

-p.

Comments

  • kb2hapkb2hap Posts: 218
    edited 2005-02-08 12:36
    There must be some other software on your machine which is interfering with the sx-key software.· I have a 2GHZ machine with 1GB of ram and 2 hard drives 120GB and 60GB over half full with software and files and have never had an issue.·(win XP home)· Go to you tasks and see what else is running while you trying to use you sx-key.· end the tasks of the programms you know until it works. I have a faster machine at work with no issues either.

    hope this helps a little

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    DTQ
  • peterjpeterj Posts: 24
    edited 2005-02-08 17:24
    Nope, it's not a driver issue or other conflict. When I brought the problem up a few months back, several other people reported similar problems on faster machines, and the issue was passively acknowledged by Parallax. In this particular case, I just re-installed my primary machine from scratch and had only a minimal software set installed when I tested the SX-Key 3.0. I'm *hoping* I can get rid of the second windows box on my desk that is there to run nothing other than the SX-Key software...

    -p.
  • PJMontyPJMonty Posts: 983
    edited 2005-02-08 19:34
    Peterj,

    Please remind me exactly what is happening when the IDE locks up. Does it lock up when you start it? When you program? When you debug?
      Thanks, PeterM
  • peterjpeterj Posts: 24
    edited 2005-02-09 00:27
    The IDE locks up during programming, typically towards the end, when the progress is between 70-100% complete. I can program successfully about 25% of the time. When I have been able to successfully program the device, debugging seems to be a bit more stable, but I have managed to lock things up in the debugger as well. The machine is an A-Bit NF7-S V2.0 mobo (NForce 2 chipset) with an Athlon XP2400+ CPU. I played with the serial port FIFO settings (as someone recomended a few months back) but that seemed to make no difference whatsoever. Everything works flawlessly on several slower machines.

    -p.
  • peterjpeterj Posts: 24
    edited 2005-02-16 06:52
    Quick follow-up here. While adjusting the 16550/FIFO settings did not have any effect with the 2.0 software, I forgot to test that with the 3.0 software. Turns out that disabling the 16550 FIFO *does* help dramatically with the 3.0 software. On the troublesome machine, I went from a 10% success rate to a 10% (perhaps less -- I just did minimal testing) failure rate.
Sign In or Register to comment.