DePbo dll

[Mikero]

>Iwant a tc plugin

it's ready today and i'll be uploading to pending in editors submissions.

it has a c, c++ and Visual Basic API, and I doubt a plugin for a desktop (such as TC) is applicable to a dll so you'll have to write your own wrapper

It's not an application as such, its the raw extractor wriiten in C++ for speed and which can be attached to any gui program like any other library.

I looked at TC but frankly, I keep as far away from the Window$ os as possible, preferring KDE desktop in linux.

[bdfy1]

Frankly speaking, I'm not a programmer at all and I have no idea how to write plugin using your api I'll post it at russian forum - may be someone can do it...
I hope you realize suport of commpressed pbo's ?
...
Source of an old TC plugin is available here
http://clubtotal.free.fr/WCX_Packer_Plugins/WCX-game_Operation%20Flashpoint-PBO_1.0%2BSRC.zip

[Mikero]

YAY!

I did it!!!

 

DePbo.dll is now avaialble at

http://www.ofpec.com/editors/list.php?show=pending

or http://andrew.nf/ofp/tools/

It understands all about compressed folders in both campaigns and missions and ALSO decrypts the so-called 'encrypted' mission sqm's and fps files.

It's a beauty, I'm really pleased with it.

You can attach it to any C++ or Visual Basic program you make.

source code supplied on request.

[Jedie]

Very cool  ;D
But, why don't you pack the sourcen directly with the DePbo.rar?

[DBR_ONIX]

Trying to use it with VB. I made new project, saved it to folder, added the module.
In the main form, made a button, then put in the code :

Code: [Select]

cd.Filter = "*.pbo"
cd.ShowOpen
PBOName = cd.FileName
thePbo = DePboOpen(tmp)

And it comes up with an error "DePBO, file not found" or similar..

If you have the VB source of something you've made with it, could you email me it, might help me understand it

Good work! Even if I can't use it currently
- Ben

[Mikero]

@DBR

place the dll in the windows/system folder
this should fix the problem.

your email address fails, so the source is now located here


@jedie

because I first want to ensure that it can be released as a slamn dunk damn easy thing to apply and use _without_ people having to resort to huge jump over left knee toeholds. Either, the dll is usable 'as is' or it isn't. That's what i want to find out.

2nd, assuming there's problems, sometimes referred to as 'undocumented features' by the very kind, I want to be able to fix them before there are 18 million different versions spread all over the internet.

[DBR_ONIX]

Ahh, that's the problem, thanks
- Ben

[Mikero]

@ONIX

let me know how you get on. I'm very curious to know if I'm right that this dll will be exceptionally usable.

[MachoMan]

Hmm I don't wanna spoil the fun, but you do know it's not good practice to place any dll in your windows folder, do you? :-\

[Mikero]

As a principle it's a bad idea (tm), exactly as putting addons in the 'official' ofp folders. But, it's also 'accepted practice' when the dll concerned is not part of a specific application. Eg, there isn't a mywhatsit.exe in a mywhatsit\ folder for the dll to be placed in. with a path=mywhatsit statement to go find it.

Don't know if you've delved into visual basic, but for vb to find a dll anywhere else than the listed default folders it searches is an excercise in futility.

all of which to say, you are right, but this was and is too convenient.

[DBR_ONIX]

dllPath = App.Path & "depbo.dll"
..no?
- Ben

[Mikero]

>dllPath=

that and const cannot be used on declare statements (unless I stopped trying too soon)

can u let me know if you had any issues with required system  ocx files? I didn't supply any.