jledesma

No, you cannot use the floppy version of the game, you have to use the game that comes with the "gamename.00x" files.

I'm also playing on a NX and yes, there are some major gripes about it, but it is due to the OS5.

Chrilith will work on our problems as soon as he gets to the 0.3.0b version of his port.

__________________
-----BEGIN PALM CODE BLOCK-----
Version: 1.1
PD f+ h b p+ o++ m++ F- v+ g+ k r+ c++ n+ t-- a++ G+ E M++ DP{T3}
------END PALM CODE BLOCK------

Draak

I know this has benn already discussed. But anyway. all seems not to work with my Clie and the fremch version of DOTT.

__________________
Resistance is futile, You will be assimilated.

Zork

unregistered, just put the 5 unrenamed .lfl files into a folder called monkey inside the games folder.

Then enter at the path monkey/ and at game monkey

Thats it.

If you still have problems try either flipping or double buffer as gfx cause they are more compatible.

chrilith

Ooops, yes you can use the floppy version of monkey 1, just put all your files on a folder and use monkey or monkeyvga as game name (don't remember wich one )

deadlyfoez

monkeyvga

Zork

chrilith, really like to finish zak256 or starting SamNMax. Any news bout the 0 bucks for Annie bug or the memory leak at the start of SamNMax ? Would be surely welcome .

jledesma

Sorry about that. I'm sure I read it somewhere in the scummv official site. I think I'll better keep quiet now.

__________________
-----BEGIN PALM CODE BLOCK-----
Version: 1.1
PD f+ h b p+ o++ m++ F- v+ g+ k r+ c++ n+ t-- a++ G+ E M++ DP{T3}
------END PALM CODE BLOCK------

chrilith

There is no prob for me with sam n max, don't know what exactly occured.

I'm currrently working on the v0.3.0b but there is few things that need to be fixed (mainly due to use of uninitialized variables on scummvm code)

Zork

chrilith, the prob with SamNMax happens on every T625 (i werent the only which searched for a save game file at this forum directly from start of the game to bypass that bug ).
So perhaps you could check the lines at the C source which is mentioned at the error code i posted at this forum ? SamNMax would be really kewl. BTW 0.3.0 is surely awesome too, but as far as i remebmer it mainly supports as new games The Dig (simply the best adventure game of all times) and Monkey 3. But both of this games couldnt be played on a PDA cause of their size (prerendered movies alone would take almost 200 MB).
So I hope that the other known bugs (SamNMax and Annie 0 bucks ) could be solved with 0.3.0 too.
BTW bout uninitialized variables. Thats horrible C developing, but at most compilers they simply would be set to zero at first appearance. Or they are used mainly as reference and during function execution their value, so the initial value (0) wouldnt matter at all. Just in case you didnt knew .

jledesma

Zork:
I know about C programming, and the variables are not set automatically to zero, they are only assigned a space in memory, and if that section of memory contains anything that value will become the variable value. So you really need to declare all variables as initialize them before you use them, otherwise you'll get a lot of strange happenings and unknown errors.

Keep up the good chrilith we're fascinated with your port

__________________
-----BEGIN PALM CODE BLOCK-----
Version: 1.1
PD f+ h b p+ o++ m++ F- v+ g+ k r+ c++ n+ t-- a++ G+ E M++ DP{T3}
------END PALM CODE BLOCK------

chrilith

In fact, this is true for PalmOS.

Zork

jledesma, start Visual C++, declare some int variable for example, set a breakpoint there and start debug mode. And one skip later you will see that the variable is set to ... 0. And as far as i remember CodeWarrior has the same behavior. Thats why i mentioned " ... most compilers ... " .

I presume that the ScummVM guys used VC (as most Windows developers do). And w/o automatic initialization to 0 it wouldnt make any sense at all to use such variables (beside the reference scenario i mentioned) and most (!) compilers would give you a warning the first time you access the value of this variable (seen such warnings during my development often, cause the horrible MFC macros hide many times the fact, that they didnt cover a class, but instead a class pointer. But the first time you compile and wondering why you get that "No initiliazing" warning, you realize ... "Hey, class pointer hidden again" . Indeed I could read bout the macro at the MSDN database, but reading manuals is just for wimps .
BTW Another reason for not initializing variables could also be that some pointer were deleted a few lines ago and when you declare a new int variable (32 bit indeed) its most likely, that its stored at the same mem offset where the pointer were formerly stored. So that could be some real brute way to store the pointer into a integer variable w/o wasting cycles by usin the load/store opcodes. But this scenario is dangerous and not really likely.

chrilith

Variables are not set to 0 or NULL by default with PalmOS and code warrior

__________________
... ...
ScummVM for PalmOS | Play your favorite Adventure games !
Click here to download the lastest release !
~
Rick Dangerous for PalmOS | Get it now !
Click here to download the lastest version !
... ...

jledesma

That's what I'm talking about And also yes, Zork is right, there are many other dangers in not declaring variables.

__________________
-----BEGIN PALM CODE BLOCK-----
Version: 1.1
PD f+ h b p+ o++ m++ F- v+ g+ k r+ c++ n+ t-- a++ G+ E M++ DP{T3}
------END PALM CODE BLOCK------