Basilisk 1.0 beta testing

@tlosm

there is disable CDROM option make shore its not on, check unit number.
And run snoopy if every thing fails.

@LiveForIt

Ok i Will try it.
This last version in all the case is more faster , but same problems with graphic and no quit button :p

@tlosm

fixed the problem i just edit the .pref in env manually i dont know why the gui continue put the cdrom in not enable state

you need to fix the 8bit gfx :P and investigate to the yellow graphic problem on the Radeon not hd card

@LiveForIt

>What videomode did you try?
>what text output do you see?
>What rom do you use?
>How much memory did you select?
>What happened?
what have you tried?
on what computer did you try it?
>Any crash logs?
>Any screen shots?

>sorry but does not work is simply too little information for me to help you.

Hello
This is allways the same Sam440 + M9 + 32 bits screen i used with the precedent binary
But now the display is fully trashed = unusable


I will note all the infos you ask + grab a screen tomorrow but right now I dont have the Sam here to make the test again...

The only thing I can say is that : I have the new binary and the old binary in the same drawer and they use the same config/hardfile/rom/screen mode and the old one is working (only) in screen mode but not the new one

The rom and hardfile were coming from my old Mac LcII
http://fr.wikipedia.org/wiki/Macintosh_LC_II
I used it for years on ShapeShifter

Alain Thellier

live for it

Just make FPU emulation working on Basilisk II 1.0 i find the config text in Env and put fpu emulation to 1 :P
why you dont set a menu for enable it ?

thanks

@tlosm

Did not know it was needed, I can fixed it now, that I know.

@thellier

So that topic has been covered before, AGP/PCI cards have this graphic corruption.

Because how things works, you need to lock and unlock p96 bitmap in order get correct endien format, so in other words video has to be buffered and copied over during a p96 lock.

I'm working on it but I want to make buffering & p96lock optional this is way it takes time.

Just tried this new version of Basilisk2 for the first time. It seems that it doesn't work with certain ROM files, but others are okay. The ROM file I used with the 0.93 version of Basilisk2 for example just causes the white screen at startup and nothing else ever happens.
But when I choose a different ROM it does boot up, as long as I hold down the right shift key to disable extensions.
On all screenmodes I've tried, I always get the "blur" effect, like the pixels are rapidly shifting to the right and back several times a second. So the display is not useable until I can figure out how to get that fixed.

Anyone have a solution?

Thanks,



Oh, I have a microA1 with the built in Radeon graphics chips.

@LiveForIt

fpu will make faster certain software and some other need it or not run :)

I tested the last mos version it gave 2.60 points on speedometer :-O

@tlosm

I don't know if FPU emulation is going to make it faster or not, it emulated after all.

@LiveForIt

No the speed of overall emaulation is the same but some Gfx programs , tools will run. Without the fpu emulation dont run.

I only test the Basilisk for Mos and speedometer geve me 2.60 cpu speed can run good Duke nukem 68k.
your version on AmigaOs is better on video emulation but compared with the mos version is slower on Cpu emulation.

I finally figured out that if I set my workbench screenmode prefs to an 8 bit display, Basilisk2 1.0 works, that is, the graphics corruption vanishes. But if workbench is in either 16 or 32 bit display mode, I get screen corruption.
Haven't done much compatibility testing yet, but version 1.0, just like 0.93, fails to run Adobe Photoshop 3.0 with an error indicating that the MAC display parameters are invalid.

Scott

@ScottCabit

Quote:

This want be a problem in the next version, there will be more options so every one will be happy.

@ScottCabit

Quote:

Well maybe its 15bit modes, as Basilisk 0.9.3 supports 16bit modes.

About version numbers of Basilisk II.

The first version number is always "1.0" or "0.9" the same as the Linux version number, the 3rd number is the version of that version, so in other words, the 1st and 2en numbers never increases unless I port a new version from Linux.

@ScottCabit

Quote:

Well maybe its 15bit modes, as Basilisk 0.9.3 supports 16bit modes.

About version numbers of Basilisk II.

The first version number is always "1.0" or "0.9" the same as the Linux version number, the 3rd number is the version of that version, so in other words, the 1st and 2en numbers never increases unless I port a new version from Linux.

a small update by Liveforit
http://lifeofliveforit.blogspot.no/20 ... es-small-blog-update.html


im really courious how will be and if will be possible have BasiliskII jit :)

@tlosm

About Jit we want know until I/we try... I don't promise anything on my part here, I will try, If I can't then maybe rachy is interested to help out.

Ilkka Lehtoranta (Itix), it might be that he as simular plans for MorphOS, we will see maybe he does it, its a possibility, if he does it we just grab what he does and rewrite it for AmigaOS4.

Possible; absolutely certain.

@LiveForIt

in all the way ... bravo! liveforit :)

Hi, thanks for the work on this.
I am trying to install 7.5.3 from a system7 boot disk.

When I add the disk, no info appears in the Basilisk info window.
When I run the emulation, the Mac starts but I simply get an image of floppy disk with a ? on it.
I cant seem to get back to the Basilisk menu or quit Basilisk

@ddni

Quote:

The combination of ROM or DISK is maybe wrong or you have corrupt file system, start whit a rescue disk instead, and try to recover the file system.

Or maybe the disk is not a boot disk.

Quote:

I where unable to force quit Basilisk II V1.0, only work whit Basilisk II V0.9.