CompuServe Thread

#Trouble Posting

6 messages in this thread
#3581From: Tim WetmoreMar 9, 1995 8:43 AM
I created a reply to a note from someone in the forum and every time I try to send it I wait and then a message saying "Timed out waiting for response" comes up and then I get disconnected from the network. I created the reply while I was in the forum and kept getting the message. I then put it in my out box and tried to reenter and send it, but I keep getting the same message. Hope you can help. Tim Wetmore
#3617From: Steve Bennett/SYSOPMar 9, 1995 8:32 PM
Tim, Please email one of the sysops, either Steve or me, a more detailed explanation of who, how, etc., you were trying to respond to and we will look into it. My knowledge of the CIS interface is not good enough to tell what may be the problem with the information that you have provided. Thank you. -John
#3634From: Tim WetmoreMar 10, 1995 8:53 AM
This is as specific as I can be: I logged on (using WINCIM) and went to the DTV Forum. I read a post Michael Towe had written in the General Information section under Future of DTV. I read it, hit the reply button, while still in the forum, and wrote my reply right there and hit the send button. The hourglass came up and I waited longer than normal and got the "Timed Out Waiting For a Response" message and then got disconnected from CIS. I then put my reply in my out basket and later tried to send it, both from within the forum and from the opening WINCIM menu and got the same response. I hope that clarifies it for you. Tim
#3646From: david bartzMar 10, 1995 1:26 PM
Tim – You might consider getting CompuServe Navigator. (GO ORDER) It really saves on the connect charges. It might even fix this problem you're having. db.out p.s. Nice Mag.
#3651From: Tim WetmoreMar 10, 1995 3:08 PM
David: Thanks, but it's the first and only time I've had trouble. Thanks for the compliment, we've gotten nothing but postivie response so far. All best, Tim
#3653From: Steve Bennett/SYSOPMar 10, 1995 5:07 PM
Tim, Did you try this again? Maybe it was a simple network interruption error of some sort. Steve is the expert here (although not neccesarily in CIM), and maybe he can think of some other gotcha. -John