Latest version of PapyBmp, with a couple of bug fixes and some restrictions removed, to be found here.

https://srmz.racesimcentral.net/index.php?s=&s...ost&p=24256

Nigel

Thanks Nigel

Splendid! A BIG TY, Nigel!

Fixed some bugs which caused crashes, but may not have got them all yet.

Nigel

Hi Nigel !

Thanks for the update.

Most work i do with WINMIP2, but a new version of PapyBmb is allways welcome.

Greetings

Achim

Nigel,
I can't make the program work.
As soon as I select a directory with graphic files, it CTD

Does it give any kind of crash offset or something like that ?

Nigel

No, it just dissapear as soon I click on a directory with some graphic files in it.

Try this debug version, it's more likely to give some kind of diagnostic message.

Nigel

Works with no problem, it doesn't give any message.
I'll try on my brother's PC tomorrow.
EDIT:
tried on my bro PC your debug version and it works troubleless on it also.
Both computers had the same "dissapear" problem with your previous version.

I was also able to use the debug version after the original one kept giving me errors and CTD. Whatever changes you made are working!

Well that wasn't really the plan, I expected the problems still to be there but maybe in a more descriptive form. I'll rebuild a non-debug version and post it in case that solves anything, since the debug version is bigger and slower.

Nigel

I've been able to reproduce the problem and this version should fix it I think - let me know if that's not the case.

Nigel

Works all right

Ooops! Looks like us TotalRankers are causing problems again!

Nigel, when I use the browser in PapyBmp (Apr 29th version from post #13 above), and open up my "tracks" directory beneath "GPL", PapyBmp stops with an assertion failure. It's probably because I have 471 tracks installed, and PapyBmp doesn't have enough buffer space to read the directory structure. The message says:

Assertion failure at .\PathName.cpp: 65
result != 0 && result < sizeof(buf)

Maybe try:

char buf[TOTAL_GREEDY_B*****D_SIZE]; ?

Actually that looks like it's a path length issue rather than a problem with the number of tracks. Do you have a particularly deep directory structure at that point ? I allow for the usual 256-ish path length - I could go for the full 32KB, but I'm not sure what other problems I'll run into in doing so.

Nigel

It doesn't seem very deep to me:

"H:\GPL 2004\tracks\" (and just to confirm, there is a space in "GPL 2004")

The 471 track directories are directly underneath there.
My original post was a bit inaccurate. When PapyBmp displays the assertion failure, I can click on "OK" and the program continues running. It tries to open up the track directory list below "\tracks\", displaying them in alphabetical order. But it stops the list partway through the "R"s. I don't see anything following, such as Spa, Watglen etc. It seems to me like it's trying to read, store and display all the track directories, but doesn't have the space to do it.

To tell the truth, I don't normally edit my tracks in the "live" installation anyway, I usually copy the required directory to a temporary location to work on it. So if it's hard to fix this, don't worry, I'll use the workaround.

EDIT: Hmm, interesting. I just tried an experiment and browsed into the directory:
H:\GPL 2004\players\Ballard__Keith\setups\
That has 473 subdirectories beneath it as it's the player I use for the TotalRank. PapyBmp opened the directory list with no problem, displayed all the names from "1320" to "Zolder" and allowed me to browse through it. Obviously it didn't display any thumbnails from there, but it showed no signs of hesitating or crashing. I'm confused!

Perhaps the windows call is failing rather than reporting that the path is long. Try this version - it should display some useful info in a message box, after which it will proceed as before.

Nigel

Ok, I tried the debug version. First I browsed into the big "setups" directory, the list came up after only about 2 seconds and with no errors. I then browsed to the "tracks" directory, the program paused for about 10-15 seconds with the hourglass showing, then displayed the following message box:

-------------------------------------------------------------
"Microsoft Visual C++ Debug Library"

Debug Assertion Failed!

Program: E:\Temp\PapyBmpDbg\PapyBmp.exe
File: C:\Program Files (x86)\Microsoft Visual Studio 8\VC\include\xstring
Line: 1536

Expression: string subscript out of range

For information on how..... (Snipped - looks like standard text)

(Press Retry to debug the application)
-------------------------------------------------------------

I then clicked on the "Ignore" button and another message box then appeared with exactly the same text, except for:

-------------------------------------------------------------
Line: 1537

Expression: ("Standard C++ Libraries Out of Range",0)
-------------------------------------------------------------

I then clicked on "Abort" and was shown a message saying an error log had been created. The error log contains:

-------------------------------------------------------------
PapyBmp Version 2,0,0,1 Error File
abort() called

Fault address: 0x7C90EB94 0x00000001:0x0000DB94 C:\WINDOWS\system32\ntdll.dll
Registers:
EAX=0x00000000 CS=0x001B EIP=0x7C90EB94 EFLGS=0x00000246
EBX=0x00000000 SS=0x0023 ESP=0x001185E8 EBP=0x001185F8
ECX=0x00118700 DS=0x0023 ESI=0x00118608 FS=0x003B
EDX=0x7C90EB94 ES=0x0023 EDI=0x00118604 GS=0x0000

Call Stack
Address Frame Logical Addr Module
0x7C90EB94 0x001185F8 KiFastSystemCallRet+0x00000000
End Call Stack
-------------------------------------------------------------

I hope that load of Chinese is helpful! (Heh, maybe "cheapracer" could help translate it!)
If you'd like me to test anything else, or press the buttons in a different sequence, just let me know.

Thanks, that wasn't quite what I was hoping for, but I think it means the path I have hold of must already be corrupted. Let me poke around for a bit and see if I can see where that may have happened.

Nigel

I'm still none the wiser, but hopefully this one won't crash while it's trying to produce the diagnostic info. You should see two message boxes, the first will have the current path and the second the return code info from the windows call.

Nigel

Nigel:
The latest debug version gives me the same exact messages that Saiph posted (except for the location of the PapyBmp.exe file). When I click on Retry, Abort and Ignore, I also get the same messages. Finally, the PapyBmp.txt error report is also the same as Saiph's.
Edwin

Hi Nigel,

I just tried the new debug version from post #21 and it behaves in exactly the same way as shown in my post #19. The only minor difference is that most of the register values in the error log are different (the fault address is the same).

Thanks guys - I didn't twig that it was crashing earlier now that you're running debug builds. Let me think a bit more.

Nigel

I found a potential problem - see if this helps.

Nigel

Woot! It works now!

Takes about 30 seconds to open my tracks directory, I was waiting with baited breath, but eventually displayed it ok. All directories appear to be shown, from 1320 to Zolder. Browsed into a few of them and the correct thumbnail images are shown. Looks good to me, well done Nigel.

Excellent, thanks for reporting back. Here's a normal build, which might be a little faster.

Nigel

and thanks again, very helpful too .

Hi Nigel !

Thanks for the "new" tool. I use a very old one. Now after the final tests i will give it a chance on my track-folder in GPL (more then 450 tracks) on my stone-old WIN98SE-system.

Greetings

Achim

EDIT: Test it with my second GPL-install (172 tracks). Works ok, so far. Opening the folder "tracks" during 15 - 20 seconds on the "+"-symbol, but close the "+"-symbol during over 2 minutes on heavy HD-activity.