posted on July 14, 2002 10:03:42 AM new
Well, Thank you anyway, Gypsygrams. It was worth a try, as we become more and more desperate. AW told me to "Install & Uninstall".
posted on August 1, 2002 12:14:01 AM new
Hi again....it has been a month...nothing has changed...its gotten worse...have all programs shut down before I open smPRO...now sometimes can't even do one listing...soon as I hit category....goner...msvbvm60.dll error, or even worse, no error, just disappears....and I have never ever had more than one batch open, am not editing a batch...just plain and simple trying to do a listing or 2 or 10...have plenty of memory, have installed, reinstalled, stood on my head, given up my first born....what is going on?????? I even downloaded 4.1 same problem!!!!!!! Will we ever get an answer for this?????
posted on August 1, 2002 09:21:23 AM new
Hi, Atomaset, I never got the solution for my problem either months later, then my computer "CRASHED!" yup, had to get it repaired, now I'm paranoid to try to install A.W. again. I think this really has gone on to long and has cost me a bundle, I think will be looking for a new listing program. Just don't know were to go I signed in with A.W. with the annual payment, now I'll have to see if they'll give some $$ back? I wish you "All Luck", Auction Watch also.
posted on August 1, 2002 10:48:03 AM new
Hi gypsy....good luck! I looked into other programs, but can't seem to find one with the post sale mgmt like this...I rely on that, but now I am lucky if I get one auction posted per hour. One auction, restart, one auction, restart....unbelievable...I was hoping 4.1 would work....nope.....I just don't know what to do anymore!
posted on August 1, 2002 10:59:29 AM new
Hi atomaset,
I am going to forward this to engineering, as I am not sure what else to suggest. You stated before that if you quit all open applications you were able to list some items before the program shut down, which makes me think it could be a resource allocation problem. Did you by any chance get a virus on your computer at any point in the past? The reason I ask is that I picked up the "love bug" virus on my system and experienced similar problems even after the virus ad been cleaned by my virus protection software.
posted on August 1, 2002 11:02:55 AM new
Hi Diana, yes, it was working before, but only if I shut absolutely everything, down, explorer, outlook, McAfee, and any IM's we had in our little bar at the bottom. I have gotten no viruses, but am very concerned that the only way I can list is to disable my programs, including my virus software...I am concerned I will get a virus while listing. But now, even with all programs shut, I can only do one, 2 tops...and that is few and far between, without restarting my computer. So how did you fix yours if it stopped working after you cleaned your virus?
posted on August 2, 2002 02:35:06 AM new
Hi atomaset,
We have only been able to replicate your problem on a computer where multiple installations of different programs had been made, and obviously some conflict among Windows system files was occurring, with memory allocation problems as a result. In that computer's case, we managed to fix it by installing the latest Internet Explorer Service Pack (which updates most of the Windows system files).
I know that you have checked The Windows Update site before... still, this is still the first line of action. Please check for critical updates, service packs, also device driver updates.
You could check also if the computer works better with the antivirus disabled. You do not need to connect to the Internet while doing this: just try to create listings and save the batch to disk. If you can create more than the regular 1 or 2 listings before a crash, then we need to look into a conflict with this software, too. Once finished with creating listings, enable the antivirus again, restart SMPro and upload the saved batch.
posted on August 2, 2002 12:24:53 PM new
Hello,
I came to this site about to loose my mind. I had been very excited about what AW has enabled me to do...until now. I am getting shut down as I am creating batches and losing everything I had just entered. The sad thing is that it worked beautifully...once. I now know that it is not me, or my computer. Since I only have this problem with this software, I am convinced that AMPro v4.1 IS the problem. I do wish you the very best, but I'm taking it off my machine until it's fixed. Glad I have a fast connection...
Kerri
posted on August 2, 2002 12:34:46 PM new
Hi Kerri,
Please keep in mind that the only users that come to the message center and post about the product are the handful of the thousands that *are* actually having trouble with it. They are far and wide outnumbered by all of the users not running into any errors.
Most of the errors can be corrected by adjustments to the machine, or software that may be conflicting, and if you did in fact want to use the software, chances are something could be done to help you get up and running if you choose to take the time to work on it.
If you do, just start a new thread outlining the error you are having, when it started, and any other details you can provide and we will be happy to address your situation.
posted on August 4, 2002 12:49:59 AM new
It is not a matter of memory allocation...or virus...or anything else AW purports to be a possible cause.
We have looked at the programming codes and protocols for SMPro, and the conflict lies purely in the fact that SMPro is written with commands to exclusivity for primary control in VB Runtime and is finding objection from both anti-virus programs and Windows patches that are defending with Script Blocking orders.
SMPro can be run with Script Blocking disabled, but that is an unsatisfactory answer, and users of SMPro should not have to manipulate programs just to satisfy the calls of SMPro when AW can easily redesign SMPro without losing any of its necessary applications. The responsibility lies with AW to affect modifications in SMPRO that will allow VB sharing and compatability.
posted on August 4, 2002 06:48:17 AM new
O.K. A.W. so is this the underlying answer to the ever on going problems "EVERYONE" is having? Has wabbitt15 found the "PROBLEM?" Will A.W. be looking into this to see if it could possibly be the "PROBLEM?"
I have made contact with A.W. Service to have the rest of my Annual Fees reimburse. If this "IS" something that A.W. can "FIX" then please get at this A.S.P. For us "FEW" that are a wits ends. And maybe like my self at the "End with A.W." Not wanting to go this route but I have no other way to go right now. Appreciate answer, also.
[ edited by gypsygrams on Aug 4, 2002 06:49 AM ]
posted on August 4, 2002 07:56:27 PM new
I too have the MSVBVM60.DLL shutdown problem - though not as often as some seem to have it. I CAN, however, cause it to occur: All I have to do is open Profile Manager while a batch file is open - AMP shuts down every ti8mewith the dreaded DLL error. If I do NOT have a batch open, I can create, delete, edit profiles with no problems. I have gotten to the point where I try to remember to SAVE the batch every 2-3 items, so I don't lose too much work, but I shouldn't have to do this.
I wouldn't even mind the shutdowns so much if it were just a matter of clicking the AMP icon and having the software load in a couple of seconds, but the fact that it has to go through the "initializing images" routine takes several minutes. I can see the need for the synchronization process each time a batch is loaded, but I don't get the "initializing images" thing. I'm sure it's probably something quite technical (??) and if the process is absolutely essential to the running of AMP, why not make it happen during synchronization, instead of every time the software loads???
posted on August 5, 2002 03:02:12 AM new
Initializing Images is a somewhat silly, unnecessary redundancy that "wakes up" the duplicate image library stored on hard drive and preps it for a comparison of what is on the hard drive to the image library stored at AW. This used to be done in synchronization, but AW asserts that it allows for a quicker and cleaner comparison of the images in order to affect necessary transfers of images that may have been erroneously deleted on hard drive, or for deletion of images on hard drive that had been previously deleted in library. Call it just a new "perk" that eats up that much more time before batch transfers can be implemented.
posted on August 5, 2002 03:13:28 AM new
Hi wabbitt15,
While SMPro uses the VB Runtime, there is nothing in the way it is written that would prevent the normal running of other programs. If you have any specific problems with "script blocking", which I assume is the Norton Antivirus feature, we would be happy to look into them; but please provide us with more information about your setup.
Hi jaymark9,
The profile problem that you encounter is a resource management issue. Windows 98 and Me are sometimes prone to such issues, and you might want to check the Windows Update site for any service packs to your Windows installation.
As for images, on restart the program is double checking your SMPro image folder for any additions or deletions that might have occurred on the local disk while SMPro was not running.
I signed in with A.W. with the annual payment, now I'll have to see if they'll give some $$ back? I wish you "All Luck", Auction Watch also. 