Interfacing Windows SDK HelloWin

[Petr Schreiber]

This is fantastic example Charles,
hardcore work - but still well structured.


Petr

[ErosOlmi]

Well, bundled exe will delete all exploded files if flag for deletion is on. So if you include "o2asm.data" file, it will be deleted.

I still prefer one of my suggestions (or any other that will not create extenal dependancies) because this creates very few confusion to users both for testing and for script distribution. But how to go with module is up to you.

Ciao
Eros

[Charles Pegge]

Yes Eros, I agree, from the modular point of view it makes sense to reduce external bits and pieces, so I will incorporate the soft coded instructions back into the Oxygen Module - after all the full source code is provided - easy to mod, so my conscience is clear

I think it is unlikely that anyone will need to customise the op codes for a particular application .- they have to be industry standard.

Should be ready later today.

[ErosOlmi]

... so my conscience is clear

Well, your conscience will be always clear.
You have provided a so great module with full source code (repeat, full source code ! ) and functionalities that you've got credits for at least 10 years!

[Charles Pegge]

Phew! that wasn't too bad. No more o2asm.data. Updated in time for your next release I hope.

There's a substantial amount of test material now which really helps with quickly verifying software mods.

Eros if you flatter me too much my head will no longer fit my hat and I will have to get a new head!

[Michael Clease]

Here is some old stuff I found which you might be interested in looking at Charles.

[Charles Pegge]

Thanks Abraxas. It's mostly 16 bit DOS but there is a windows 95 32 bit demo in the 'companion disk' folder, using TASM with macros and prototypes.