Basilisk 2

< bump >



@LiveForIt

Just checking in... Things going well? Need any beta testers?



Thanks,

PJS

@pjs

Last time i spoke with him he was finishing the gui,and was trying to solve the network which was not working. Fixed some minor bugs like not freeing up memory on exit.

@pjs

I have ethernet support almost working, maybe some one else can have look at sourcecode, I don't understand way it does not work, way it lockup.

@all

Elwood will be showing Basilisk 2 on the Alchimie show in France

@LiveForIt

excellent !! thanks for your work...

@LiveForIt

Thats good news

Is it working as it should now?

And when is the show?

And who forgot to adjust the clock this weekend and was 1 hour too early at work?

@LiveForIt

I think that Basilisk2 does something nasty.
When it is running (even on the GUI, i.e emulation not running), when I type the command "dumpdebugbuffer", it doesn't return, like if a forbid() was still current.
Strange.

@Elwood

Quote:

If was a forbid problem you world not be able to type "Dumpdebugbuffer" in shell

And increase stack to 1000000 before starting the emulator, it often helps other programs.

The GUI has busy loop type of event handler, that's way might eat more CPU cycles running the GUI then when the emulation is running, some whit reaction skills can fix that in a second.

I have not tested the emulator on the July update,
so far I have only tested on OS4 Final update.

@LiveForIt

Quote:

Why not hardcode this stack value in the executable itself by adding a line like :

@abalaban

I don?t really know the amount of stack used,

Any way the stack should be predefined in the icon.

@LiveForIt

Quote:
Hum, a Wait() shouldn't eat up al the CPU power.

@Elwood

Yes, I?m not using WaitMsg() or Wait(), I?m using GetMsg() that?s way, now go ahead and fix the problem.