MicLandShark
Novice
Reged: 08/16/03
Posts: 2
|
|
Hello all,
I am sad to report that i believe I have found a limit on ESSC.
I have 384 megs ram GeForce2 64 meg AGP video card Athlon 1.333 mghz cpu C: drive = 10 gig hard drive 4 gigs free D: drive = 20 gig hard drive 10 gigs free (where i keep SlideShow) Windows ME OS Sound Blaster Live sound card.
I have a slide show that currently displays in the program 325 pictures. Plus i have 5 wave files attached and synchronized to my pictures.
I have ran this 12 times and every time i get the same error
"StartSlideShow has caused an error in BudAPI.x32:
StartSlideShow will now close. If you Keep experiencing problems try restarting."
I have restarted my computer 12-15 times. Everytime I get the same place in the Show and it crashes.
When I started my trouble shooting process I was in shock of my findings.
The Picture it kept crashing on was number "256"!!!!!!! And than it hit me! this must be an 8 bit program "pointer List"??
Is this the limit of the Slideshow?? I thought we were all on 32 bit platforms!!
SO i am just asking is this normal or Did I do something wrong.
thank you MicLandShark
MicLandShark@comcast.net
Edited by MicLandShark (08/16/03 09:23 AM)
|
Jeremy
Journeyman
Reged: 11/20/02
Posts: 49
Loc: Columbus, OH
|
|
Hello,
I'm sure Brad will comment soon, but int he mean-time, does it fail at 256 every time, even if you remove that picture? It could be a corrupt file for example. Also, please make sure you have version 1.22, available now on our site. We will figure this out, don't worry!
-------------------- JS [EOTT]
|
Brad
Addict
Reged: 11/20/02
Posts: 220
Loc: O-H-I-O
|
|
Hi, I think I may have found and solved the problem. Please download and install this version and let me know if it works for you:
http://www.programmingart.com/products/slideshow/beta/slideshowsetup-1_23.exe
If I'm right, it seems that a 3rd party library may have been causing the problem, and it was in fact happening on the 256th item. The funny thing is that this library was not being used in any "list" capacity where you would typically be limited to some fixed size array, but it was on the 256th function call, so there must be some sort of internal call tracking within the library that used a fixed size container. Thank you very much for such a detailed problem report, it's a great help to have so much to work with.
-- Brad
-------------------- --
Brad Ishida
Programming Art, LLC
http://www.programmingart.com
|
MicLandShark
Novice
Reged: 08/16/03
Posts: 2
|
|
That seemed to do the trick:):):):):):)
It played all my files in that slide show.
I am not going to be funny but when i get done I'll have about 520 slides. I'll see than if it hangs on 512???
I dont think it will.
Thank you very much for the patch. Any time I could be of service just let me know!!!!
David
|