Menu
▾
▴
basilisk-user — Basilisk II discussion for users
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2003 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Russell S. <rj...@ip...> - 2003-10-28 12:34:31
|
Hi, I've installed BasiliskII 1.0 from a debian package, as well as compiling from cvs. I'm using a quadra 900 ROM that was verified to work with Basilisk on a friends win2k box, and i've tried numerous mac boot disks from the net. These have names like System 7.5.5.dsk, Basilisk_Linux_disk.dsk, and System70_boot.zip etc. I've tried using dd or xhfs to raw-write them (.zip was decompressed first) to an hfs debian floppy drive (i've got hfs enabled in the kernel 2.4.20), as well as booting from them on the HDD. I always get errors like: Basilisk II V1.0 by Christian Bauer et al. Reading ROM file... Using /dev/dsp audio output (speakers make slight humming noise) Caught SIGSEGV at address 0x14110380 [IP=0x80d5e0d] D0: 00000000 D1: fffcffff D2: fffffffc D3: 0400000f D4: 0003fffc D5: 00000000 D6: 00000012 D7: 00000000 A0: 0000003c A1: 00000002 A2: 00006d40 A3: 0000714c A4: 00006934 A5: 04110380 A6: 00000000 A7: 020009a6 USP=00000000 ISP=020009a6 MSP=00000000 VBR=00000000 T=00 S=1 M=0 X=1 N=1 Z=0 V=0 C=0 IMASK=0 FP0: nan FP1: nan FP2: nan FP3: nan FP4: nan FP5: nan FP6: nan FP7: nan N=0 Z=0 I=0 NAN=0 0402e8e8: 2815 28c4 c081 c284 8287 MOVE.L (A5),D4 next PC: 0402e8ea The floppy drive light flashes momentarily when Basilisk boots. System is P-III 500MHZ with 256MB ram. What makes a mac floppy bootable? Is it the presence of a certain file? Does it need to be in a certain physical location? What linux tools should i use to copy a floppy image to the disk? What extension should the floppy file have (.dsk/.hqx/ etc?) What downloadable floppies are there that are known to work in linux? (All the tutes are for windows tools). I tried tracing thru basilisk with GDB, but basilisk exits before getting very far. What's the best way for debugging? (i'm interested in how it works) I assume i only need a rom file and a boot floppy to atleast see some action from basilisk? |
|
From: Rhonda H. <0x7...@pa...> - 2003-03-04 04:02:11
|
Hello, I was wondering if somebody could help me with a serial port problem I'm having with Basilisk II running under Linux. And before you ask, yes, my permissions allow me to use the ports - in fact, they're wide open: # ls -l /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3 crwxrwxrwx 1 root uucp 4, 64 Dec 14 01:09 /dev/ttyS0 crw-rw-rw- 1 root uucp 4, 65 Jul 17 1994 /dev/ttyS1 crw-rw-rw- 1 root uucp 4, 66 Jul 17 1994 /dev/ttyS2 crw-rw-rw- 1 root uucp 4, 67 Jul 17 1994 /dev/ttyS3 And I know I'm pointing at the right one (ttyS0 in this case) because another program was talking to that same device on that same serial port. It's having its own problems - crapping out partway through a data transfer - but it is setting up the connection successfully. I'm not sure if this is related. Anyhow, back to the question. Basilisk, and the app running, both lock up hard, requiring a kill from the console, whenever I try to release the serial port. It seems that way, anyhow. I can select the serial port to use, try to connect, whatever, but as soon as I try to deselect the serial port or close the connection program, Basilisk locks up and MacOS gives me shit the next time I start it for not letting it shut down properly. What I've tried: mapping the "printer" and "modem" serial ports in Basilisk to both physical ports, and swapping them; mapping only one, then the other; connecting via one, then the other. It acts the same regardless. The app in question is "Newton Connection Utilities", and the device in question is a Newton, if that helps at all. The newton mailing list hasn't been able to help me beyond pointing me at this fine program at the start. Well, that and providing a mac OS 7.5.something disk image with NCU pre-installed. I should probably focus on getting Basilisk talking via ethernet, and having my Linux box route appletalk, since connecting to the newton via ethernet is much faster, but this serial thing is bothering me and I want to get it fixed first. Call me obssessive if you want to :-) I hope it's some stupid thing that I'm forgetting and somebody will point it out and call me an idiot and I'll happily connect to my Newton. Please? -Rhonda -- www.write-on.indy || write-on.homeip.net \/ http://history.ubcengineers.ca/ Discuss the art and craft of writing /\ UBC Engineers History Project That's the problem with world domination. Nobody is willing to wait for it anymore, work slowly towards it, drink more and enjoy the ride more. |
|
From: Stefan M. D. <sd...@sd...> - 2002-12-27 14:00:17
|
Can anyone help me how I do fix the undefined reference on a standard RedHat 8.0 Intel Box ? gcc -o obj/gencpu obj/gencpu.o obj/readcpu.o obj/cpudefs.o obj/readcpu.o: In function `build_insn': /work/BasiliskII-0.8/src/Unix/../uae_cpu/readcpu.cpp:201: undefined reference to `__gxx_personality_v0' collect2: ld returned 1 exit status make: *** [obj/gencpu] Fehler 1 Thanks a lot ! |
|
From: Carsten N. <de...@sn...> - 2002-12-14 05:19:24
|
Hi all, my `unsupported ROM' problem occured because I erroneously assumed the RO= M's size is 1MB. This was because my ROM extractor always reads 2MB and the IIci ROM image= file contains junk in every 2nd 512KB block. But V1.0 still crashes. So I went back to V0.9 and Basilisk II boots fine. But I can't change the error sound, can't use AppleTalk, and can't set th= e timezone. There are probably other problems which I haven't found yet. I think this could be a PRAM problem. But I can't go to V1.0 because it crashes: Basilisk II V1.0 by Christian Bauer et al. Reading ROM file... Using /dev/dsp audio output do_handle_screen_fault: unhandled address 0x446a4700 [IP=3D0x80a414e] D0: 00000000 D1: fffcffff D2: fffffffc D3: 0000000f D4: 0003fffc D5: 00000000 D6: 00000012 D7: 00000000 A0: 0000007c A1: 00000002 A2: 00006658 A3: 00006a6c A4: 0000624c A5: 04291700 A6: 00000000 A7: 020009ae USP=3D00000000 ISP=3D020009ae MSP=3D00000000 VBR=3D00000000 T=3D00 S=3D1 M=3D0 X=3D1 N=3D1 Z=3D0 V=3D0 C=3D0 IMASK=3D0 FP0: 0 FP1: 0 FP2: 0 FP3: 0 FP4: 0 FP5: 0 FP6: 0 FP7: 0 N=3D0 Z=3D0 I=3D0 NAN=3D0 0402e8e8: 2815 28c4 c081 c284 8287 MOVE.L (A5),D4 next PC: 0402e8ea Thank you for your patience, sorry for the noise, =09Carsten --=20 Certify your minority, support spyware! Soon to come as TCPA and Palladium from Microsoft & Co. |
|
From: Carsten N. <de...@sn...> - 2002-12-12 18:24:03
|
Hi all, I am new to Basilisk II, although I did some (unsuccessful) attempts on i= t for over one year. There are several problems with CVS and CVS snapshots. I use linux kernel 2.4.17, glibc 2.1, gtk 1.2.6, latest BasiliskII snapsh= ot/checkout. The minor problem is that autogen.sh fails on the CVS checkouts, this is = probably partly an autoconf problem but if one could give me a hint...! ;-) The macros AC_DEFINE, AC_MSG_WARN, AM_PATH_GTK, AM_PATH_ESD are `possibly= undefined'. After commenting out the code for handling the GTK and ESD stuff in `conf= igure.ac' the `configure' script is built but gets stuck (doesn't terminate) on checking if GCC is = >=3D 2.7 (I use 2.95.3). The major problem is that I get `Unsupported ROM type' errors on the CVS = snapshot. I get these for IIfx and IIci ROM images. Both are 32 bit clean and I couldn't read anything that they are unsuppor= ted. I've enabled debugging in rom_patches.cpp and found that the InitMMU patc= h failed. After changing the (ROMSize > 0x80000)-branch of the if statement to the = same as the (ROMSize <=3D 0x80000)-branch I get a lot further, but then I fail: see attachment for the IIfx ROM including ROM info. It looks like Basilisk II isn't tested with IIfx and IIci ROMs. Is there anything I can do making it work for these? Kind regards, thank you, =09Carsten --=20 Certify your minority, support spyware! Soon to come as TCPA and Palladium from Microsoft & Co. |
|
From: Christian B. <cb...@th...> - 2002-02-08 11:21:02
|
Hi! On Thu, Feb 07, 2002 at 12:29:58PM +0100, Hende Roland wrote: > When i tried to compile the basiliskII, i got this message: > checking for X... disabled > configure: error: You need X11 to run Basilisk II. > > what can i do? Look in config.log to see what's missing (probably an XFree86-devel package). Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ |
|
From: Hende R. <rol...@st...> - 2002-02-07 20:29:58
|
Hi all! When i tried to compile the basiliskII, i got this message: checking for X... disabled configure: error: You need X11 to run Basilisk II. what can i do? best regards honza debian woody, 2.4.17smp, dual piii 800 |
|
From: Gwenole B. <gb...@di...> - 2002-01-15 16:50:49
|
> And, yes, it's now Basilisk II V1.0. :-)
BTW, is the m68k->x86 JIT compiler supposed to be for 1.0 or should we
stabilize until 2.0 with a ppc->{x86,x86_64,[ia64]} as well? ;-)
Bye,
Gwenol=E9 in <hopes> mode.
|
|
From: Christian B. <cb...@st...> - 2002-01-15 15:36:20
|
Hi! On Tue, Jan 15, 2002 at 04:33:05PM +0100, Gwenole Beauchesne wrote: > > I've made a new CVS snapshot of Basilisk II you can get it from: > > <http://iphcip1.physik.uni-mainz.de/~cbauer/BasiliskII_src_15012002.tar.gz> > is probably what you meant. ;-) Uhm, yes. :-) Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ |
|
From: Gwenole B. <gb...@di...> - 2002-01-15 15:32:27
|
Hi Christian, > I've made a new CVS snapshot of Basilisk II you can get it from: > http://iphcip1.physik.uni-mainz.de/~cbauer/BasiliskII_src_31052001.tar.= gz <http://iphcip1.physik.uni-mainz.de/~cbauer/BasiliskII_src_15012002.tar.gz> is probably what you meant. ;-) Bye, Gwenol=E9. |
|
From: Christian B. <cb...@st...> - 2002-01-15 15:22:21
|
Hi! I've made a new CVS snapshot of Basilisk II you can get it from: http://iphcip1.physik.uni-mainz.de/~cbauer/BasiliskII_src_31052001.tar.gz The changes from the last snapshot are quite significant, with run-time video and audio mode switching being the most useful one. A more complete changelog is here: http://iphcip1.physik.uni-mainz.de/~cbauer/BasiliskII/ChangeLog_snapshot And, yes, it's now Basilisk II V1.0. :-) Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ |
|
From: Christian B. <cb...@st...> - 2001-06-01 14:16:50
|
Hi! Basilisk II 0.9 has now been released and can be downloaded from the usual places (http://www.uni-mainz.de/~bauec002/B2Main.html and SourceForge). Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ |
