BasiliskII for windows revived!

[Cat_7]

Well, your wish has just come true:

We are talking about compiling a new version of BasiliskII through the use of a cygwin installation on windows. Gwenole Beauchesne has kindly worked out a version that compiles using these tools with an all new jit-compiler.
What you get (if everything goes well) is a BasiliskII executable for windows.

Seeing the last post by mac emu thing DO work. (congratulations)

Best wishes,

Cat_7

[Cat_7]

Hello,

Got my
-rom file that used to work in basiliskII for windows,
-the prefs file and
-the executable I build in the same directory.
Basilisk gives me: cannot open rom file

Below is a listing of the directory. I used the prefs file AZEnigma kindly provided and adapted it to my situation.

If everything was well I should be able to start basiliskII from within Cygwin using "./BasiliskII"
Right?

-rw-r--r-- 1 Administ Domain U 488 Nov 21 01:25 .basilisk_ii_prefs
-rwxrwxrwx 1 Administ Domain U 1997293 Nov 21 00:30 BasiliskII.exe
-rwxrwxrwx 1 Administ Domain U 1901826 Nov 17 17:13 Mac_OS_ROM
-rwxrwxrwx 1 Administ Domain U 1048576 Nov 28 2003 QUAD650.ROM

Has anyone got any idea what goes wrong?

Cat_7

[Jack Hair]

Hello,

Got my
-rom file that used to work in basiliskII for windows,
-the prefs file and
-the executable I build in the same directory.
Basilisk gives me: cannot open rom file

Below is a listing of the directory. I used the prefs file AZEnigma kindly provided and adapted it to my situation.

If everything was well I should be able to start basiliskII from within Cygwin using "./BasiliskII"
Right?

-rw-r--r-- 1 Administ Domain U 488 Nov 21 01:25 .basilisk_ii_prefs
-rwxrwxrwx 1 Administ Domain U 1997293 Nov 21 00:30 BasiliskII.exe
-rwxrwxrwx 1 Administ Domain U 1901826 Nov 17 17:13 Mac_OS_ROM
-rwxrwxrwx 1 Administ Domain U 1048576 Nov 28 2003 QUAD650.ROM

Has anyone got any idea what goes wrong?

Cat_7

Im having the same problem it seems as if the config doesnt work properly, i found out when i enter all options on the commandline it works on cywin and windows. After trying lots of stuff i just made a .bat file, seems to do the trick. Here's how i start it on windows running macos 8.1:

basiliskII --disk Macos8.hfv --disk Macprogs.hfv --udptunnel true --udpport 6066 --bootdrive 0 --bootdriver 0 --rom quadra.rom --ramsize 134217728 --frameskip 0 --modelid 20 --cpu 4 --fpu true --jit true --jitfpu true --jitdebug false --jitcachesize 8192 --jitlazyflush false --keyboardtype 5 --keycodes false --mousewheelmode 1 --mousewheellines 3 --ignoresegv false

[Cat_7]

Hello,

Big thanks!

It works.

Cat_7

[wiebeest]

We are talking about compiling a new version of BasiliskII through the use of a cygwin installation on windows. Gwenole Beauchesne has kindly worked out a version that compiles using these tools with an all new jit-compiler.
What you get (if everything goes well) is a BasiliskII executable for windows.

But I allready have Basalisk II under Windows...what's the big difference?
Googled Cygwin:
"What Is Cygwin?
Cygwin is a Linux-like environment for Windows. It consists of two parts:
A DLL (cygwin1.dll) which acts as a Linux API emulation layer providing substantial Linux API functionality. A collection of tools, which provide Linux look and feel."

So, why use a Linux emu under windows emulatiing basalisk II,
while there allready was regular Basalisk II for windows...???
What am I missing here?

[Cat_7]

Wiebeest,

You have to understand correctly: Cygwin is used to compile basiliskII in a unix-like envirnoment, but it creates an executable for windows.
So you can run the new BasiliskII in windows.
Basilisk now has the latest jit-compiler features, although it misses the GUI and easy configuration options that Basilisk for windows has.

But what is more important, in my opinion at least, is that this will be a first step for the developer to make SheepShaver, the PowerPC (g4) emulator that is based on Basilisk, available to the windows platform.

If that isn't somethinh to look forward to, I don't know what is
I guess the development of Basilisk and SheepShaver has had a boost by the successes of Pearpc.

Best wishes,
Cat_7

[Cat_7]

Some performance remarks:

if you change
--jitlazyflush false to true
in the config string things get more lively.

Cat_7

[gb]

You should not need to pass command line arguments. The prefs file must reside in your home dir (~/.basilisk_ii_prefs). Otherwise, a default one is generated there and that one is used. i.e. a .basilisk_ii_prefs file in the directory containing BasiliskII.exe has zero effect, AFAIK.

[Jack Hair]

You should not need to pass command line arguments. The prefs file must reside in your home dir (~/.basilisk_ii_prefs). Otherwise, a default one is generated there and that one is used. i.e. a .basilisk_ii_prefs file in the directory containing BasiliskII.exe has zero effect, AFAIK.

.basilisk_ii_prefs seems to work indeed, exept for my hardfiles and rom, it just wont take it unless i enter them on the commandline. Also .basilisk_ii_xpram doesnt seem to save my screenmode, nor does the screen option in .basilisk_ii_prefs or commandline work, i have to set my screen in MacOS every time i boot BasiliskII.

Exept for these minor problems BasiliskII runs really good 8)

[wiebeest]

Basilisk now has the latest jit-compiler features, although it misses the GUI and easy configuration options that Basilisk for windows has.

I see. So that is what all these compiling-lists you are posting in this thread are all about. But anno 2004 IMO GUI is the only way to go beyond geekness. I know once people were used to typing commands on a regular basis. But that was in the DOS-era. I had my share of cd.. cd\ dosshell dir, etc , but that time is long gone.

Eversince probably 1996 people got used to pc's with pre-installed win95 GUI shells to control their pc's and I guess I'm a victim of this advancement too. I can only hope one day (hopefully sooner than later) there will be a GUI available for this new Basalisk II. Say, why has Basalisk II evolved for Linux, but has it stopped for win32 since build 142 (which was January 2001).

But what is more important, in my opinion at least, is that this will be a first step for the developer to make SheepShaver, the PowerPC (g4) emulator that is based on Basilisk, available to the windows platform.

Now you got my attention...does this mean OS 8.5 possebilities,
perhaps OS 9?

If that isn't something to look forward to, I don't know what is
I guess the development of Basilisk and SheepShaver has had a boost by the successes of Pearpc.

I like this forum. Very interesting indeed.
Since I get the chance now to really discuss the thesis, without getting flamed...why can't a PPC-capable emulator like a newer version of Basalisk II not run OS X?
And why is OS X on pearpc so much S L O W E R that OS 8.1 on my win32 Basalisk II? Please don't direct me to the reading material on some of the websites, because it's way too technical for my limited comprehension of English.

ERGO: Could any of you guys explain to me in common words why a Basalisk II version that can emulate a PPC on x86 can not run OS X?

Thank you beforehand.


WiebeEST

[robojam]

I think the short answer to that is that there are major architectural differences between OS8 OS9 and OSX that make emulation of each of them a very different animal.

[niuus]

Will there be a binary posted for us non-power linux users? :D

[Jack Hair]

Will there be a binary posted for us non-power linux users? :D

http://members.home.nl/mikel77/BasiliskII.zip

There u go - its the Windows version packed with SDL and cygwin DLL's, and without GTK

http://members.home.nl/mikel77/BasiliskII-GTK.zip

This is the GTK version - Only runs with CygwinX

[wiebeest]

Will there be a binary posted for us non-power linux users? :D

There u go - its the Windows version packed with SDL and cygwin DLL's, and without GTK
This is the GTK version - Only runs with CygwinX

Ok, thanks, but...how do we use it?
Do I install it in my allready existing Basalisk II directory,
overwriting the old ones, or what?
Plain unzipping and clicking the .exe doesn't seem to work.

Any advice?

[Cat_7]

From what I read some posts above:
you start the new basilisk with a command line just like below. Fill in your file locations for ROM file and hard disk file.

The best thing to do this is to make a .bat or .cmd file containing the command line.


basiliskII --disk Macos8.hfv --disk Macprogs.hfv --udptunnel true --udpport 6066 --bootdrive 0 --bootdriver 0 --rom quadra.rom --ramsize 134217728 --frameskip 0 --modelid 20 --cpu 4 --fpu true --jit true --jitfpu true --jitdebug false --jitcachesize 8192 --jitlazyflush true --keyboardtype 5 --keycodes false --mousewheelmode 1 --mousewheellines 3 --ignoresegv false

Best wishes,
Cat_7

[Jack Hair]

After starting BasiliskII for the 1st time, u can find the basilisk_ii_prefs in your windows home folder (e.g. C:\Documents and Settings\Your Name). Might be easier than a .bat

[gb]

It's also possible to build a cygwin-less binary of Basilisk II. The added value of this one is CD-ROM support, My Computer style icon, networking with NAT-Router stuff of virtual ethernet driver (b2ether).

Almost all code is in CVS (the main parts). At some point in the future, you may be able to build it yourself too.

[niuus]

Thx Jack Hair :D

[wiebeest]

After starting BasiliskII for the 1st time, u can find the basilisk_ii_prefs in your windows home folder (e.g. C:\Documents and Settings\Your Name). Might be easier than a .bat

in that path I find the file .basalisk_ii_prefs,
which (when opened with notepad) contains the following (and I quote):

"extfs /
udptunnel false
udpport 6066
bootdrive 0
bootdriver 0
ramsize 8388608
frameskip 6
modelid 5
cpu 3
fpu false
nocdrom false
nosound false
noclipconversion false
nogui false
jit true
jitfpu true
jitdebug false
jitcachesize 8192
jitlazyflush false
keyboardtype 5
keycodes false
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
ignoresegv false"

No idea what to do next. I've got a ' Starterdisk.hfv'
and an 'osdisk.dsk' (from my old windows version) how do I make the .exe aware of these disks, so that it can use them?

[Mac Emu]

Add to the .basilisk_ii_prefs file

disk /osdisk.dsk

and put osdisk.dsk in the Cygwin directory.

[wiebeest]

Add to the .basilisk_ii_prefs file

disk /osdisk.dsk

and put osdisk.dsk in the Cygwin directory.

Thanks. Will try. I wonder if it'll work...and work faster.
I'll be back.

[Marc]

rom D:\macemu\BasiliskII\quad650.rom
udptunnel false
udpport 6066
bootdrive 0
bootdriver 0
ramsize 134217728
frameskip 6
modelid 5
cpu 3
fpu false
nocdrom false
nosound false
noclipconversion false
nogui false
jit true
jitfpu true
jitdebug false
jitcachesize 8192
jitlazyflush false
keyboardtype 5
keycodes false
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
ignoresegv false"
disk D:\os8.hfv

Here is my config file and I get 'cannot open rom file'
and then crash

any ideas??

[Mac Emu]

If you have Cygwin installed, use

rom /quad650.rom

after placing the ROM file in your root Cygwin directory.

You will have to do the same with your hdf.

[Marc]

Got it to work, thanks

Is it so slow for everyone else?!

[Jack Hair]

Got it to work, thanks

Is it so slow for everyone else?!

The mouse is a little choppy when the CPU is busy, but the rest isnt slow for me. U could try to put this in your config, for a littlie speedup:

jitcachesize 16384
jitlazyflush true