Recent Posts by Lazlo
|
Aug 24, 2010
|
Morgan, as you can tell from all the posts since August 8 when you released 2.1.1, there are a lot of problem. Drag and Drop doesn’t work, but most importantly, the auction history is all messed up. For me, it’s parsing the dates on the closed auction incorrectly, so all the auctions are listed in the wrong order. Others are posting that they’ve lost their entire auction history, which sounds like a database issue. I’m also having the problem that others are reporting that auctions will spontaneously be marked as over, when they’re still running, and auctions that have completed get “stuck” on the active auction list, and don’t get moved to the history. |
|
Aug 24, 2010
|
Likewise, drag and drop stopped working. I gather Ebay has changed the auction header again. |
|
Aug 12, 2010
|
I’m having problems with the completed listings as well — JBid doesn’t seem to parse the complete date correctly, so all the completed listings are out of order. |
|
Feb 9, 2009
|
Another confirmation of the failed snipe on 2.0beta11-736 Events |
|
Oct 18, 2008
|
This is the same Pre-Snipe login bug that all the other posters are having problems with. JBidWatcher is broken for now, until Morgan re-writes the login code. |
|
Oct 18, 2008
|
This is the same Pre-snipe login failure bug that all the others are having problems with. |
|
Oct 18, 2008
|
Yes, Ebay has broken JBidWatcher again. I reported this problem at the beginning of October, sent email to Morgan, and there are nearly a dozen identical bugs filed about this problem. JBidWatcher tries over and over to log in to your Ebay account, the login protocol is failing, and Ebay locks the account with a “Captcha” thinking that it’s a bot trying to hack into your account. Then you have to stop running JBidwatcher for several days to reset the Captcha. I’ve lost at least 6 auctions in the last 2 weeks because of this bug :( |
|
Oct 18, 2008
|
JBidWatcher has a serious bug with the latest Ebay login protocol. I’m losing about 20% of my snipes because of the “Pre Snipe Login Failed” I’d really like to hear an answer from Morgan, there are several reports of this same bug here (including my own), and there are nearly a dozen identical bugs filed on the bug tracker. This is one of my auctions that just failed because of the Pre-Snipe Login bug: Sat Oct 18 13:55:57 CDT 2008: Sat Oct 18 13:55:57 CDT 2008: 220293547536 (FAFNIR 2MM203WI DUL SUPERPRECISION BEARING, NIB) – Preparing snipe. Sat Oct 18 13:56:14 CDT 2008: Did not successfully retrieve the sign in cookie. |
|
Oct 4, 2008
|
“the login did not cause any errors and delivered cookies , but was not clearly recognized as successful”. Morgan, I’m getting the same thing with 2.0beta8—the login fails, and then triggers the Ebay Captcha crap, and then I have to turn off JBidWatcher for a couple of days to re-set the Ebay security monitoring. I’m guessing that Ebay is now checking for automated logins, and JBidWatcher constantly updates the Ebay login cookie, so it looks like you’re logging-in to Ebay over, and over… |
|
Sep 3, 2007
|
By the way, there also seems to be a serious problem with JBidwatcher 1.0.2 synchronizing time with the Ebay server clocks. Aside the several time-synch issues reported in this thread (including mine), there are a slew of similar bug reports on the JBidWatcher SourceForge bug tracking page: http://sourceforge.net/tracker/?atid=103914&gro… I’ve been using JBidWatcher for years (on the same computer) and have never had the time synch issues before… |
|
Sep 3, 2007
|
Cyberpip, I don’t see any posts in this thread where Morgan talks about 1.0.3pre1. JBidWatcher 1.0.2 is now completely random—sometimes the snipes fire, sometimes they don’t, but even when the snipe does fire JBidwatcher can’t understand the response from the Ebay servers, and gives you an error message that “Snipe failed for unknown reason” (when you actually won the auction). “The only problem I forsee is that I have to agree that ebay seems to be trying to prevent snipping software from working since it helps prevent running up the bids and costs them money.” Ebay is more than happy to support sniping programs. They even provide a software developer’s toolkit to help you write Ebay software. The problem is that they charge for the software developer’s kit, and Morgan can’t continue to release JBidWatcher as freeware if he has to buy the Ebay developer’s kit. It sure look like Ebay is trying to “encourage” Morgan to buy the developer’s kit by constantly changing the Ebay server messages to throw-off software developers who haven’t purchases the official Ebay software kit. |
|
Aug 29, 2007
|
“It probably has something to do with eBay’s new beta pages.” I don’t think so—I just had another snipe fail with the same “Failed to load from server” error. I think it’s pretty obvious that Ebay is randomly changing the server handshake messages to discourage software developers who haven’t purchased the Ebay API/SDK. Does anyone have any other snipe programs they could recommend? |
|
Aug 26, 2007
|
JBidWatcher isn’t working at all now. I just had two auctions close, and JBidWatcher didn’t fire the snipe at all: Events |
|
Aug 24, 2007
|
Hi Morgan, I just had a “no prior bids” snipe that triggered with the same message. The one I posted above had bids on it—I’ll check the debug message in a couple of minutes… Robert |
|
Aug 24, 2007
|
So yesterday I got an error message that the snipe didn’t trigger, but I won the auction anyway??! Events |
|
Aug 20, 2007
|
“I am still having time sync issues. Never had it with 1.0, or 1.01.” Likewise. Something has changed. |
|
Aug 16, 2007
|
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
|
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
|
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&i… Currently: $86.03 (5 Bids) |
|
Aug 11, 2007
|
Morgan, I just checked the JRE debugger this morning, and there’s no memory leak—JBidWatcher stabilized at 31 MBytes. Thanks again!!! Robert |
|
Aug 11, 2007
|
Thanks Morgan! When I cleared the deleted tracking, JBidWatcher no longer deleted the auctions.xml file. I think I found a memory leak though: I set the debug.memory flag, and I’m getting 509.1 MB Max Memory, and 80 MByte of memory in use (this is with a 4 MByte auctions.xml file). If I hit the GC key, the Memory Use drops to 17.3 MByte, but then steadily increases: it’s up to 34 MByte 5 minutes after I did a garbage collection. I’ll leave it running overnight – I’m curious to see what the memory usage is in the morning… Cheers, Robert |
|
Aug 10, 2007
|
By the way Morgan, one other nuisance issue: since 1.0, JBidWatcher will pop up an “Unknown Sniping Error” bubble if the snipe value is below the current auction price at the programmed snipe time. I’m assuming this is because JBidWatcher is not parsing the message from Ebay that the snipe amount is below the current minimum bid. Cheers, Robert |
|
Aug 10, 2007
|
Hi Morgan, I’ve been having a problem with JBidWatcher 1.0.2pre5 and 1.0.2pre6 deleting the auctions.xml file, and restarting from scratch. I have a very large auctions.xml file (around 4 MByte) with all my Ebay activities over the last couple of years (which I keep for price comparisons). If I delete the auctions.xml file and replace with the last dated auctions save file (auctions-10Aug07_1034.xml), everything works fine until the next time I launch JBidwatcher, and then it deletes the auction.xml file again. Cheers, Robert |
Topic: