Olympus-OM
[Top] [All Lists]

[OM] [OT] iSnipeIt - I can't get it to work

Subject: [OM] [OT] iSnipeIt - I can't get it to work
From: Chuck Norcutt <norcutt@xxxxxxxxxxxxx>
Date: Thu, 22 Mar 2001 18:17:15 -0500
Sorry, guys, this is pretty far OT but I figured there's probably as
much or more expertise on the Oly list for this topic as anywhere else.

I waited for about 6 months for the right Kiron 70-150 to come along on
ebay and lost it to a snipe at $1.00 over my bid.  I also waited for
about 6 months (the second time) for a '99 Chrysler LHS factory manual
to come along and also lost it to a snipe for $1.00.  Durn!!! Time to
try sniping myself.

So, I ordered the trial version of iSnipeIt and all works OK except that
it can't dial and connect by itself... pretty useless for an auction
ending at 2:00 am.  I have created two dialer profiles on my Win2000
machine.  One uses the standard Windows dialer, the other uses the AT&T
dialer provided by attglobal.net (my ISP).  If I start either one of
these dialers manually all is OK.  I can then start IE 5.0 or Netscape
4.76 and either will happily find and use the existing connection.  For
that matter, so will iSnipeIt.

However, if I start IE 5.0 first and allow it to intiate the dialing I
get some peculiar results.  It seems to form a connection but then
complains bitterly that it can't find the server.  I assume that this is
the same thing that's going on when I ask iSnipeIt to control the
dialing since it uses IE under the covers.  iSnipeIt dials the phone,
connects and then complains that the connection was terminated. 
iSnipeIt gets worse if I attempt to use the AT&T dialer profile.  It
quits instantly without even attempting to dial and then gives me the
same bogus message that the connection was terminated.

I sent a message off to iSnipeIt's publishers asking what they might
know about this but I'm being ignored... not surprising on a $25 package
I guess.  Anyhow, I'm stumped.  I've tried dialer configuration settings
till I'm blue in the face.  They have to be correct since they work just
fine if I start them manually.  Am I facing an IE 5.0 specific bug? 
Anybody got a clue?

Thanks,
Chuck Norcutt
Woburn, Massachusetts, USA
(tired of getting sniped)

< This message was delivered via the Olympus Mailing List >
< For questions, mailto:owner-olympus@xxxxxxxxxxxxxxx >
< Web Page: http://Zuiko.sls.bc.ca/swright/olympuslist.html >


<Prev in Thread] Current Thread [Next in Thread>
Sponsored by Tako
Impressum | Datenschutz