Login  •  Register


The time is now: Tue Jul 22, 2014 3:30 pm

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 1 of 1 [ 15 posts ]
Print view Previous topic  |  Next topic
Author Message
PostPosted: Thu Jun 16, 2011 5:31 pm 
Offline
Space Cadet

Joined: Thu Jun 16, 2011 4:59 pm
Posts: 8
Location: USA
I have had not had any problems with Basilisk running under OS X 10.4.11 on a PowerMac G5. Starts very quickly, I can print to a network printer, and I can surf with iCab. All this is using Mac OS 7.5.5 in Basilisk.

I have recently put a second hard drive in my G5, have installed OS X Leopard (10.5.8) and chose to do a fresh setup of Basilisk, scrupulously (I think) following the guide posted here.

I installed Mac OS 7.6 and updated to 7.6.1.

It runs, and seems OK superficially, but if I run Basilisk, and then exit it, Leopard will not shut down or restart properly. I see a pinwheel on the screen for 5-10 minutes, and end up pushing the power button to force a power off.

If I don't launch Basilisk II, no such problems; shutdowns and restarts are nearly instantaneous, as is usual for Macs.

I also set up an LPR printer in my new Basilisk installation, but it just won't print. Printer utility verifies the IP OK, I have the correct PPD, but all print jobs hang at 80% and then give a -25003 error.

I did notice that my "hard drive" for Basilisk in Tiger is an NDIF disk image, with the .img extension.

Not so in Leopard - it's just an icon.

I'm about to give up on Basilisk II in Leopard, since I am going to maintain a dual boot machine. I have given some thought to copying my Basilisk "hard drive" to Leopard and have Basilisk try to mount it instead of my OS 7.6 one.

Is it possible that Basilisk II gives an "orphan" process after it shuts down in Leopard, and that is what is preventing my Mac from turning off?

Any ideas would be appreciated; I'm curious as to what could be wrong.

I am aware of one mistake I made - I had a file on my OS 7.6 desktop that came from the "Unix" HD, and I tried to move it to the trash and empty it, and got an error message. Could all of these problems stem from this event?


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Thu Jun 16, 2011 7:48 pm 
Online
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 3370
Location: Sittard, The Netherlands
Hi,

To start with your last remark: I don't think that's a problem.
When you start Basilisk, is it through the basiliskGUI application? Does that application shut down when you shut down Basilisk? If the basilisk windows closes, the application itself should be gone. Only the GUI can sometimes stay active. A long shot would be to check whether there are other, perhaps conflicting, applications running that only make problems after having been active together with basilisk.

You could check for orphan processes through the utilities/activity monitor tool.
You can indeed copy your disk image to your Leopard installation. If all GUI settings are the same, then the functionality should also be the same. It would be a good test to see if your new mac os 76 installation is to blame.

The icon for the hard disk shouldn't matter, I've seen no problems with disk images. In the end they are formatted by mac os when you initialize them at installation. An 8.1 installation can use HFS plus, while a 7.6 installation can only be on HFS.

Best,
Cat_7


Top
 Profile  
Post a reply  
 Post subject: Thanks
PostPosted: Thu Jun 16, 2011 8:16 pm 
Offline
Space Cadet

Joined: Thu Jun 16, 2011 4:59 pm
Posts: 8
Location: USA
Yes, I launch Basilisk using the Basilisk II icon - the green "dragon". Not the Basilisk II GUI one uses during initial setup.

I shut down by shutting down OS 7.6 - Special, Shutdown.

Basilisk II shuts down promptly - the green dragon exits the dock.

Yes, I have considered using Activity Monitor to see if Basilisk spawns something that stays on, or if there is unusually high hard disk activity.

I may try using my image from Tiger, as it is known to behave well (at least on Tiger).

I have also considered deleting my Basilisk nvram and prefs files and starting fresh. Something seems very wrong.

I've even considered reapplying my OS X 10.5.8 Combo Update, although, as I said, everything seems great as long as I don't use Basilisk.

As you may gather, I am reaching the point where I will just leave Basilisk on the Tiger disk; I don't feel like doing an archive and install in the remote chance it might make Basilisk coexist with Leopard. I don't know what the cause is, but I'm not happy when I can't shut down the computer.

I should also mention that when I was setting up OS 7.6, I was moving a lot of files around on my desktop, and in and out of the Shared/Unix folder (disk images and such).

At one point, things got cluttered, and I dragged items to OS X trash and told Finder to empty the trash. Finder said it couldn't, because a plist file was in use. So, I held down the option key while emptying the trash. Soon after that, these problems started.


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Thu Jun 16, 2011 9:07 pm 
Online
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 3370
Location: Sittard, The Netherlands
Hi,

About that remark about the plist file: Basilisk doesn't use those files. You might have inadvertantly trashed a system file.
A simple test with a copied disk image and new prefs/nvram created through the GUI isn't that much effort and could shed light on your situation. At least with respect to basilisk being the culprit or not.

Did you use the migration wizard to migrate your account/apps to leopard? That has caused problems earlier, which were indeed fixed by re-applying the 10.5.8 update.

Best,
Cat_7


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Thu Jun 16, 2011 10:50 pm 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 3980
Location: Amsterdam, Netherlands
I remember a similar (or even the exact same?) problem reported here some time ago. I do not remember whether it was solved. Maybe try a search in the forum to find that other thread.


Top
 Profile  
Post a reply  
 Post subject: More information for you
PostPosted: Fri Jun 17, 2011 2:53 am 
Offline
Space Cadet

Joined: Thu Jun 16, 2011 4:59 pm
Posts: 8
Location: USA
I didn't use the Migration Assistant for my applications. This new Basilisk setup was from scratch, following the latest guide.

I did go into Console, and found the following (please excuse the length of this). I found a couple of these errors when launching in Tiger, but not these many, many reiterations of WARNING: RmvTime.

This shows what was going on between when I shutdown Basilisk and when I attempted (unsuccessfully) to restart the system.

Thanks again for your assistance. Leopard was restarted using a Safe Boot, and seems very responsive and no issues.

I think trying one more time, completely fresh start, after removing NVRAM and Prefs, with my old "hard drive" is worth a try.



Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: Basilisk II V1.0 by Christian Bauer et al.
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: Reading ROM file...
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: Using SDL/coreaudio audio output
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: VOSF acceleration is not profitable on this platform, disabling it
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: FATAL: Could not reallocate framebuffer at previous address
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(000fd7a8): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0fcae718): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0fcae4d8): Descriptor not found
Jun 16 07:09:55: --- last message repeated 20 times ---
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0fcae718): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(000fd7a8): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0feb0018): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0feafdd8): Descriptor not found
Jun 16 07:09:55: --- last message repeated 16 times ---
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0feb0018): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0feafdd8): Descriptor not found
Jun 16 07:09:55: --- last message repeated 1 time ---
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0feab328): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0feab0e8): Descriptor not found
Jun 16 07:09:55: --- last message repeated 22 times ---
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0feab328): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0fe2bc68): Descriptor not found
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0fe2ba28): Descriptor not found
Jun 16 07:09:55: --- last message repeated 26 times ---
Jun 16 07:09:54 gordons-power-mac-g5 [0x0-0x9d09d].BasiliskII[670]: WARNING: RmvTime(0fe2bc68): Descriptor not found
Jun 16 07:10:32 gordons-power-mac-g5 kernel[0]: { 41 810400} UniNEnet::restartReceiver
Jun 16 07:10:47 gordons-power-mac-g5 loginwindow[342]: DEAD_PROCESS: 0 console
Jun 16 07:10:47 gordons-power-mac-g5 shutdown[702]: reboot by gordon:
Jun 16 07:10:47 gordons-power-mac-g5 shutdown[702]: SHUTDOWN_TIME: 1308226247 466934
Jun 16 07:10:47 gordons-power-mac-g5 com.apple.loginwindow[342]: Shutdown NOW!
Jun 16 07:10:47 gordons-power-mac-g5 mDNSResponder mDNSResponder-176.3 (Jun 17 2009 18:57:52)[22]: stopping
Jun 16 07:10:47 gordons-power-mac-g5 com.apple.loginwindow[342]: System shutdown time has arrived^G^G


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Fri Jun 17, 2011 6:07 am 
Online
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 3370
Location: Sittard, The Netherlands
Hi,

Only one line in your log worries me:
BasiliskII[670]: FATAL: Could not reallocate framebuffer at previous address

This happens when Basilisk can't allocate memory after a restart. Can you try to up or lower memory allocated to Basilisk in the GUI? How much are you using right now?
Are you using our latest Basilisk build from here:
http://www.emaculation.com/forum/viewtopic.php?t=5887

Best,
Cat_7


Top
 Profile  
Post a reply  
 Post subject: Update
PostPosted: Fri Jun 17, 2011 2:18 pm 
Offline
Space Cadet

Joined: Thu Jun 16, 2011 4:59 pm
Posts: 8
Location: USA
I am using October 4, 2009 Basilisk.

I deleted my Basilisk PRAM and Prefs, and brought in my hard drive image from Tiger.

No more problems with shutting down or restarting.

My CPU, memory, ROM, and Model IDs were also copied directly from Tiger

RAM Size - 128 MB
Mac Model ID - I believe it says MacIIci, System 7.x - NOT Quadra 900, System 8.x
CPU Type - 68040
ROM - Quadra 650 - NOT Performa.ROM

I don't have Ignore Illegal Memory Accesses checked

I do get the FATAL framebuffer error in Tiger, too.

I have the Performa.ROM from Redundant Robot (Performa 630), and would be willing to try RAM = 64 MB, Quadra 900, and Performa.ROM. If it makes FATAL go away, and Leopard can still shut down and/or restart, I would be happy. If the changes bring back hundreds of error messages and the inability to shut down my computer, I'll have mixed feelings.

I'll try all the changes and let you know the outcome.

Thanks


Top
 Profile  
Post a reply  
 Post subject: Follow-up
PostPosted: Fri Jun 17, 2011 4:02 pm 
Offline
Space Cadet

Joined: Thu Jun 16, 2011 4:59 pm
Posts: 8
Location: USA
If I change Machine ID and ROM, should I do a new clean install of the OS so that the OS installer "install System Software for this machine" makes the OS agree with the new "hardware"?


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Fri Jun 17, 2011 11:02 pm 
Online
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 3370
Location: Sittard, The Netherlands
Hi,

I'm not sure. The only thing I do know is that both roms should work whether you run OS 7 or 8.
The difference between the machine models deceides whether you can install mac os 7 or 8, as their descriptions say
I'm also not sure which cpu's were around at the time OS 7 or 8 where released.

I would do a clean install after changing the model id as it effects the software you can run, but not after changing the cpu type.

Best,
Cat_7


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Sat Jun 18, 2011 12:57 pm 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 3980
Location: Amsterdam, Netherlands
I am not sure either, but I suppose that indeed the machine ID will influence the installation.

I myself use BasiliskII MacOSX (10.4, 10.5, and 10.6) with Quadra 640 ROM, model ID set to Quadra 900, and CPU set to 68040 for all three systems I have installed, 7.5.3, 7.5.5, and 8.1. I never used model ID Mac IIci.


Top
 Profile  
Post a reply  
 Post subject: Final Update
PostPosted: Mon Jun 20, 2011 1:54 pm 
Offline
Space Cadet

Joined: Thu Jun 16, 2011 4:59 pm
Posts: 8
Location: USA
OK, I went ahead and did a clean install.

I'm now running OS 7.6.1, LPR printing works, and I can access the Web using iCab. Basilisk starts quickly and seems stable, and I can restart or shut down Leopard after using it.

I am using Performa ROM, Quadra 900 as Machine ID, and 64 MB of RAM.

No luck whatsoever in getting the FATAL: framebuffer error to go away. This persists in both Tiger and Leopard, with 3 different ROMS, and RAM settings everywhere from 16 to 128 MB, using Mac OS 7.5.5, 7.6 and 7.6.1.

No combination has been found yet which will affect that. Other than that, Basilisk seems to be doing everything I could want it to do.

I believe the only thing I have not yet tried is disabling sound.

Anyway, I thank both of you for your input. It looks like I will have to live with the framebuffer error. Perhaps with a dual G5 PowerMac, that is unavoidable.

[/b]


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Tue Jun 21, 2011 12:58 pm 
Offline
Granny Smith
User avatar

Joined: Fri Aug 27, 2010 1:02 am
Posts: 125
Get a Intel mac, PPC Macs will be outdated soon.


Top
 Profile  
Post a reply  
 Post subject: Re: Get an Intel Mac
PostPosted: Tue Jun 21, 2011 2:10 pm 
Offline
Space Cadet

Joined: Thu Jun 16, 2011 4:59 pm
Posts: 8
Location: USA
julialy wrote:
Get a Intel mac, PPC Macs will be outdated soon.



Your "assistance" may or may not be relevant to this issue. Neither moderator has said anything to imply that there are any problems with running Basilisk on PowerPC, it's a Universal build.

It's also a little odd to see this here, as the whole point of running either Basilisk or Sheepshaver is to maintain the ability to run older Mac software.

I currently am using two Macs, one's a PowerMac 8500 (1995), the other is my PowerMac G5 tower (2005), both of which I enjoy immensely. My previous Mac was a Mac II (1987). All have been very solid, reliable equipment, and I enjoy Macs partially because they don't become paperweights in 2 years; my replacement cycle has been 8-10 years, as you see.

I don't hate Intel Macs, and my next Mac, in 2-4 years, will be one (unless Apple goes to AMD processors). But I don't feel that I need to run out and buy one soon


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Tue Jun 21, 2011 2:39 pm 
Offline
Granny Smith
User avatar

Joined: Fri Aug 27, 2010 1:02 am
Posts: 125
Basilisk II works best in Intel, for best performance upgrade to Snow Leopard and Intel.

(I don't hate PPC)


Top
 Profile  
Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 1 of 1 [ 15 posts ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
 

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group