Re: A snapshot of the LuxAsm developments

From: The /\\\\o//\\annabee (Faq(Sqeeeek!)_at_.@szmyggenpv.com)
Date: 12/20/04 

Date: Mon, 20 Dec 2004 14:24:47 +0100

> _____
> Sorry...can't help you. ((( `\
> I don't do WinDoze. Hehehe! _ _`\ )
> (^ ) )
> ~-( )
> _'((,,,)))
> ,-' \_/ `\
> ( , |
> `-.-'`-.-'/|_|
> \ / | |
> =()=: / ,' aa

Sure. Then I cant help you neither Annie. The question about hw-drivers
for dr.dos was half serious anyway. Not to make fun of you or anything. I
like you, you know. You're funny & cute and wonderful, Annie.

However. Maybe someone else can be helped. My report about the
virtualalloc problem, isnt really serious, while there are many ways to
work around it. I found now that the bug appear only when blocks of memory
become very large. And I also miscalculated the allocated memory.

I ran a few test, and it seens that I can safely use a block as large as
320*1 200 000, and in all fairness, I could make that much smaller, by
parsing the Win32FindData, during the scan, allthough this would
drastically slow down the scan. Thats why I am not going to do it. But 1.2
million files is not bad, and it turns out to work for both XP and NT. And
the best thing is that this time, when the reservation is that "small" it
_is_ properly released/managed. If its bigger, then ..... crash ! :-(

So I made one version for XP, which can handle as much as 3 million files,
and one version for NT&XP that can handle a maximum of 1.2 million files.
The XP version can handle even more files, as the XP memorymanager is
simply less flawed then NTs. But also, the problems in the NT version, is
just as much a problem in XP. This takes a lot more space to explain. So I
will just not do it. But here are the links for the beta version of
Monster Media Ex (someone named it Monster LOL, and thats fine, I am
pretty proud of it anyway).

The XP ONLY version is here :
http://www.szmyggenpv.com/downloads/MMEXBlue.Zip

and the NT & XP version is here :

http://www.szmyggenpv.com/downloads/BlueNT.Zip

And the full source code, is included inside the exefile, and will compile
with RosAsm without any need to do anything but load the exe in and press
compile. ALL of RosAsm programming is this easy. If you used C++ and
Delphi or the like, you should conclude : WOAH thats awesome. And yes
kids. It really IS awsome. Go get some.

< http://betov.free.fr/RosAsm.html >

I still suspect there are bugs in my demos, but I have been using the XP
version for a month with no problems.

Also, for people interessted in starting RosAsm programming I moved the
Streaming code into the CurrentProject and the "CurrentProject" will now
be able to save all its memory in the same way as the DirectShowDemo
(MMEX). This means that it will allways remember the exact state of the
internals of the application, between runs.

Heres is that link :
http://www.szmyggenpv.com/downloads/CurrentProject.Zip

This has allways been the plan. To create an app that will allways go
straight back to its previous state, without ever reading any inifiles, or
the fucking stupid retarded registry. Personally I have many ideas for
what this can be used for, but one things is clear, using a technic like
this, you'll never have to write ANY spesific configuration-saving/loading
code again.

Can you say incremental ?

So just add to it, (CurrentProject) and it will continue to work, If you
take note of the problems with the large blocks. Later next year I will
release a full extensive documentation of how to use the SOOAP library
without running into problems. I think its better to write an OOP library
reference when I am done. And I am far from done. It just end up beeing
constantly changed, and I hate writing such docs, so thats why.

I need a sig. Now take a hike.

the /\\o//\annbee.
( Selfproclaimed Minister of propaganda. RosAsm camp.) 

--