Posts that ToKa is monitoring
Aug 17, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Who can sent me 1.0.1.1 for macOSX? |
Aug 17, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! I’ve reverted back to an old version JBidWatcher-1.0.1.1.jar which still seems to be working ok. Updates fine, able to add new auctions ok, not tested sniping yet. Steve |
Aug 17, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Hi Morgan, I am using the latest version of your program. Regards |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Greetings,
Right; this is in ms, so it’s about a 7.2 second difference (including network latency) between your computer and eBay. That tells me that either eBay or your computer are sliding a lot more than they should be, because if you’re synched to a time server, and eBay is as well, then you and eBay should be nearly dead-on. So here’s the way it probably played out. Your computer’s clock was behind by about 30 seconds. JBidwatcher determined the time delta was around 30 seconds with latency, and so scheduled the snipe to occur at 13:00:27, because in eBay time that’d have been 12:59:54 (giving enough time for the bid submission to occur). Your computer hit what it thought of as 13:00:00, did a time-resynchronize, corrected the time (which was probably fast), and when 13:00:27 actually rolled around, it was the real 13:00:27, and the auction had been over for 27 seconds. The combination has more to do with the pre-snipe and snipe events bracketing the time synch operation, than 1.0.2. It’s something you really shouldn’t run into very often, first because it means your clock lost more than 27 seconds in an hour, and second because auctions aren’t often listed precisely at the hour. … I don’t offhand know how to fix this. If your computer’s clock drifts and is corrected while JBidwatcher is trying to place it’s bid, I’m really not sure what JBidwatcher can do… :( I’ll think on it for a bit, but I’m pretty confident it’s a rare problem. While I do that, you should also probably look into why your clock skews so quickly; most people only need to synchronize time once a week or once a month. Once an hour is…a lot. — Morgan Schweers, Cyber*FOX*! |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Hi Morgan, I’m not sure how to interpret the results of the Time Information Window: Current time: Thu Aug 16 17:32:02 CDT 2007 I’m guessing that’s in milliseconds, so the clock delta in 6.6 seconds? |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Greetings, Hrm… If your clock is regularly synchronized to a time clock, it really shouldn’t happen, unless eBay’s clocks are messed up (which I saw once, but not often since then). Go to Servers | Time Information, and post what it shows… It won’t tell us what the time delta at the point of bidding was, but it’ll tell us how much difference JBidwatcher thinks there is now. Also, do you know when the time synchronization happens? — Morgan Schweers, Cyber*FOX*! |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Wow, I’ve been using JBidWatcher for years, and never had that problem before. I’ve got my Windows XP desktop synchronized with one of the internet atomic time clocks (time.windows.com) once an hour, and my snipe delay is 5 seconds… Just a coincidence that this happened with JBidWatcher 1.0.2? |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Greetings,
This looks like JBidwatcher thought your system clock was incorrect (a little fast) by at least 30 seconds, probably more like 60, since the end time of the listing was 27 seconds before that. It’s possible it was wrong, or that your system clock corrected between when it last determined that, and the snipe time. JBidwatcher tries really hard to adjust for clock skew, but it’s not perfect. — Morgan Schweers, Cyber*FOX*! |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! I just had an auction fail Morgan. The snipe value was way over the final closing price, and the message was that the auction could not be bid on anymore because the auction had closed: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=170137709249 Currently: $86.03 (5 Bids) |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Greetings, Well, first I would ask that you check what version of JBidwatcher you’re running, by opening up the Help | About screen, and looking in the upper left, next to the image, to see if it’s 1.0.2, because that’s exactly the 1.0.1 error. I’m not seeing that error, loading auctions… I notice you removed the actual URL that you had an issue with. I nearly always need specific auction numbers that fail to try and replicate the problem. — Morgan Schweers, Cyber*FOX*! |
Aug 16, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! In just a very short time, looks like eBay made changes once again that won’t allow auctions to be added. I get the message “Cannot add auction http://cgi.ebay.com/……, either invalid or communication error talking to server.” Drats! And I just wanted to thank you for all the hard work in developing such a friggin’ awesome program. |
Aug 11, 2007
|
Topic: [Release] JBidwatcher 1.0.2 is now available! Greetings, I’ve put up the latest version, 1.0.2 of JBidwatcher. It incorporates fixes for all the issues that have plagued JBidwatcher over the last 3 weeks, and several more besides. More information is available on the the JBidwatcher homepage, and will be available in the JBidwatcher 1.0.2 changelog when I get around to writing it. :)
As always, best of luck with your auctions! — Morgan Schweers, CyberFOX! |