Packard Forum Index » General

BigKev,

As Ron and Eric said, only every 3/4/5/6 attempts worked and we also tried alternating.

Are there any protocols/rules that we need to observe because we're all in there together? I wouldn't think so because that's what it's designed to do. This is the luddite in me thinking out loud trying to clutch at anything which may have an impact.
The refresh time was also re-set by all of us to 5 seconds from the default 20 seconds but this didn't help either. It seemed that when I tried to write a longer chat that these failed almost all the time, I did keep in mind your advice there could be a character limit so kept them not too long. While there did seem to be more, but not always success with short/shorter chats. Maybe Ron and Eric can confirm or deny an "old-timers" thoughts.

Please Kev, weave your special magic and allay the natural fears of this pathetic luddite.

Hmmm weird. I will take a look at the coding and see what I can come up with. The original free source code was pretty spagetti, so there may be core timing issues with it. I will take a look.

Just tried it and it wouldn't take any of my posts...

BigKev,

There were a bunch of us in earlier and the same problem was evident. I joined Tom(Packin31), Scott Naspora and J.D.inK.C. joined a little later and we all experienced it.

Polish up that magic wand, or sort out the code if you must. As we're all hanging on waiting for it to work and enjoy the fruits of your labor.

Ok guys give it a beating now and see if it breaks. Some of the special characters and punctuation were causing the SQL database commands to fail. I had to add some special code to handle those, and it should now work. I was able to replicate this problem over and over with the exact same message. Once I added the code to compensate for the special characters, then it worked just fine. Hopefully this was the monkey wrench in the machine.

Thanks for bearing with me. As always I try to fix things as quickly as I can once I can determine where the gremlin lies. I would have tracked it down sooner, but I am currently traveling for business. Thanks to Mal for the punctuation suggestion that sent me looking in the right direction.

Thanks to Mal for the punctuation suggestion that sent me looking in the right direction.

[/quote]

Kev, It was only a little more than dumb luck on my part to suggest the punctuation and I'm glad it worked. Of course, given enough time I would have suggested anything and everything anyway.

I'd give it a test but at 7:25pm Wednesday evening Sydney time it must be well past midnight Pacific coast time there and other forum members are currently non existant.

A big thankyou from all the guys(and girls) for your endeavours.

Kevin, I'm glad you fixed it! I personally wasn't using any special punctuation, other than periods at the end. Even so, it's a big kudos to you on how fast you get things fix here, and if you were closer, I'd have you working on my Pat!!

BigKev,

Another matter, somewhat minor, so I suggest it be left until you're back from your road trip. I minimised the Chat room window thinking if there was a chat post it would "beep" to let me know. But no "beep", so either I'm deaf, it didn't work, my laptop doesn't have sound or it's not turned on. I'll follow up on the laptop aspects with my son who I inherited the laptop from recently so he'll know whether the sound works on it or not.

So - No rest for the wicked Kev.

Same here, no beep. I'm on a Mac using Camino if it matters.

I get the beep using Firefox on a Dell laptop.