<offtopic>
I had some big trouble with my MacMini G4 last few days. The hard disk stopped working and gives sounds like from a head crash. I removed the drive and just boot from CD without problem. Than I ordered a new SSD drive and it arrives yesterday.
I try it and find out that as long as the new SSD or the old HD is inside (both use IDE bus) not even the CD drive is working. I try all the tricks (press c, press alt or use Openfirmware commands to boot from CD) but all fail. I also reset the NVRAM and the PRAM without making it better.

CD drive is only working if I remove the HD or SDD from IDE bus. Maybe the IDE controller has an error or the power rail due to an defect cap I don't know. I ordered this 9 year old mac mini just a month ago at Ebay.

Because I want to cross check SSD and HD with other computer I ordered an USB to IDE adaptor yesterday, but it needs some days till the adapter will arrive.

Somehow in the evening I managed it to install MOS on an external USB drive and configure the Openfirmware to boot always from USB. My feeling is that when using USB the system is not as stable as with IDE before. But this impression could be wrong since I start to play around with different screens. And maybe just the feature of multiple screens is unstable anyway and it is not related to the USB drive.

After I have checked the SSD in the next days I will decide if I order a new PPC hardware or not. I still don't know what I will do next.
</offtopic>


Anyway with the USB drive workaround solution I try to install WB 3.1 with E-UAE-0.8.29-PPCJIT_BETA03_MORPHOS and E-UAE-0.8.28-2.

E-UAE-0.8.28-2 was working without problems (good find Jambalah thanks), but E-UAE-0.8.29-PPCJIT_BETA03_MORPHOS has the same issues as E-UAE-0.8.29-WIP3 and WIP4 and sucks at 12%.

[ Edited by Waitsnake 27.07.2014 - 12:21 ]

> maybe just the feature of multiple screens is unstable anyway

I'm not aware of any unstability induced by using multiple screens.

Oh, there are many ways to get problems. E.g. this one here:
1.) MOS prefs -> Screens -> New sceen
2.) Open Odyssey
3.) Right click to go to "MUI..." prefs of Odyssey -> Screen -> assign to new screen from 1.)
4.) select "Bearbeiten ..." (guess in english it is called "Change ...") to change settings of this screen
5.) change "background picture" of this screen -> where Texture.png is preselect change it to maybe Winter.jpg than OK -> OK -> Save
6.) very often now I get a new window called "log server" with "Public Screen Manager" and "Unknown Exception"
After this exception most times my main Ambient screen is gone and I only have the Odyssey screen left, but with that screen I can only surf the web till I close Odyssey an than I can not do anything else than move the mouse arround or make a cold restart with the power button.

Or afer the reboot from last screen crash (see 1.) to 6.)) I do:
7.) open Odyssey in its own screen now with it's own Winter background -> nice no problem till now
8.) go back to Ambient screen while Odyssey screen is still open
9.) open Morphos prefs -> Screen -> make a new third screen maybe for MPlayer
10.) close Screens preferences with "save"
11.) Again I get "Log Server" window with "<>" and "Unknown Exception"


I don't know if it could be related that my hole MOS system dunning on a slow sdcard inside USB stick and system using all the ti,e Poseidon USB stack while normaly system would run over IDE hard drive?

Or maybe my hole system has some serious hardware problems? This is the thing that MOS relates to Hardware that is not longer manufactured and I had to buy an 9 year old computer at Ebay with no clue about it's conditions. It's a bit sad because I really like the look and feel of MOS since I play around with it for a month or so... I even would prefer it to OSX that I use since 10.3. if only all things would be a bit more stable.

If it is only my hardware I would look for a nother "new" old hardware at ebay... but there is allways the risk that this mashine has also problems since it will be at least 9 years old too.

[ Edited by Waitsnake 27.07.2014 - 15:16 ]

> I don't know if it could be related that my hole MOS system dunning on a slow sdcard inside
> USB stick and system using all the ti,e Poseidon USB stack while normaly system would
> run over IDE hard drive? Or maybe my hole system has some serious hardware problems?

I followed your steps while running MorphOS from PATA and couldn't reproduce your result. I think you should file a bug report. This way, the MorphOS Team could determine with your help whether it's a hardware problem at your end or a MorphOS bug.

Quote:

This is nothing unusual and not a hardware failure. In the early days ide devices had many issues, when being used on the same IDE bus. It got better and better over the years, but never was perfect.

Especially the drives used in Apple devices are often problematic in this case. It also happens, when using SSDs in PowerBooks.

These devices simply do not like each other. Another issue is that in many cases you cannot change the master/slave mode, as it is hard coded/soldered or stored in firmware. Check if there is a jumper on the CD drive and remove/plug it, if possible.

Replacing the harddrive along with the CDROM drive however is the best solution in most cases.

Geit

Finally I buy a second MacMini at Ebay. Exact same model as before (1,5GHz 1GB RAM with 80 GB HDD). I found out that RAM of this 2nd MM is defect and CD-ROM reads much much worser than the CD from my 1st MM. But this are issues that I can fix with replacement parts in future if I will.

Anyway I used this 2nd MM to cross check/replace all the components step by step with the 1st MM (the power supply, the HDD, the SSD, the CD-Drive, the logic board and this mini bridge board that connects CD/HDD to logic board).

Finally I come to the conclusion that the problem that causes the trouble was the SSD. So the suggestion of geit was correct:
Quote:

The original 80GB HDD works in both machines and CD drive is than not blocked, while with the SSD the CD drive was missing. For those how wants to avoid the same problems I use an "KINGSTON SSDNow KC380 120GB 1,8 microSATA3" together with an "Adaptare 46234 Adapter". Maybe it is this IDE 44 pin to Micro-SATA adapter that causes this problems with both MM.


Than just for luck I ordered an other SSD this time an "Transcend TS32GPSD330 interne SSD 32GB" that has direct an IDE 44 pin interface and not needs an adapter as my 1st SSD.
And what should I say? This SSD works perfect in both MM and not have any side effects to the CD drive.

Quote:

Do you use MOS 3.6 with Chrysalis pack 3.6.1 beta ?
Because during my hardware experiments and fresh installations I realize that with an blank/clean MOS 3.6 I had also NO issues with the screens. Just after installing Chrysalis pack that was of cause an still an beta I get this problems.

Anyway now it is MOS 3.7 out and also Chrysalis pack 3.7.1 beta and I will repeat my tests with this version in the next days. In Chrysalis pack 3.7.1 Papiosaur removed something in the Ambient prefs that "caused problems". Maybe this causes problems with the screens as well? We will see.

[ Edited by Waitsnake 07.08.2014 - 13:46 ]

> Do you use MOS 3.6 with Chrysalis pack 3.6.1 beta ?

No Chrysalis here.

> with an blank/clean MOS 3.6 I had also NO issues with the screens. Just after
> installing Chrysalis pack that was of cause an still an beta I get this problems.

This explains why I don't have these problems.

What is the problem with pack 3.7.1 please ?

As I mention in the post #93 and #94 creating a few screens with their own background and assign them to different applications is a bit unstable.

I notice that I don't had any problems when booting from a 3.6 or 3.7 MOS-CD or when using a fresh install of MOS. But after I install the pack 3.6.1 / 3.7.1 I get these problems.

I don't know for sure if it is really related to the Chrysalis pack or if it could be still an issue of my hardware. Maybe you can try to repeat the steps and play a little with the screens creation to see if it is reproducible or not.

Thanks Waitsnake, i will do some tests but it's very strange...

Do you have a Mac mini with 32MB of graphic memory ?

No, I have one with 64 MB.

Nice. Thanks to the contributions in this thread, I managed to install WB 3.1 on a blank hardfile.
I went further and installed Amiga OS3.9 along Boing Bags 1&2 and Picasso96.
At reboot, it shows a message saying that it "cannot open uae.device unit 3" and even if the
installation of P96 and uaegfx went smooth, I only get PAL modes in "ScreenModes".
I'm not really into E-UAE, so:
A 68020 cpu with
chipmem_size =4
fastmem_size=8
z3mem_size=32
is enough to support P96modes?


scrAb_

> even if the installation of P96 and uaegfx went smooth, I only get PAL modes in "ScreenModes".

Do you use the SDL version of E-UAE?

Given that this thread has become alive again, I have a couple of questions:

1) What's the maximum floppy speed value on the config? Is it "800"?

2) Is it possible to add floppy sounds on latest e-uae jit v 1.0? If yes, what's the config entry and has anybody the .wav sound set uploaded somewhere?
From what I read RuninUAE has such capability in OS4, so it must be doable in our universe as well, I suppose..

3) I followed the instructions how to launch an application inside UAE from Ambient (I am trying with PPaint 7.1c for AmigaOS 3.x) but I somehow failed to succeed. Just to get it straight, by choosing "Run in UAE" on the 68k executable, it will launch (my previously set up) full 3.1. environment which will automatically call the application I requested? And if I close the application (i.e. PPaint), I let UAE running on the background and choose "Run in UAE" on a different 68k executable, it will reuse my active UAE?
Perhaps I have messed up where the scripts point to, will conduct more tests within today. However, is there any more transparent way of launching the classic application? You know, under a window which won't state UAE on the top, running a visible 3.x setup underneath etc..

[ Edited by Cool_amigaN 13.03.2015 - 12:52 ]

@Andreas

Yes, the SDL version.
I tried to run Work:Picasso96/Debug/CheckBoards, and it complain about missing board
and suggests to "Start Monitor first".
Right now I'm googling about it...

...and found that it only need to add "gfxcard_size=...." to .uaerc, so that
it can detect a gfx card :)

done.


scrAb_



[ Edited by scrAb_ 13.03.2015 - 22:42 ]

Quote:

1. max 800%
2. add to .uaerc floppyXsound=1 (X = 0-3)
e.g.
floppy0sound=1 -add sounds for df0:

@Norbi

Thanks, it worked!

If you have any idea for 3rd question, I would be eager to hear about it as well :)

Quote:


Have you replaced the rexxsyslib.library (m68k)

Just checked, had on sys:libs/ version 36.23 (17/04/1991) and I replaced it with the newer v. 44.1 (25/12/1999) from my OS3.9 installation. I 've put the library in MOSSYS:Libs as well (the dummy was already disabled) just in case, but still no go :(
If I click Run in UAE it gets me until it has fully loaded the 68k enviromed (3.9).. I 'll check my s-s for the uaercli command just in case btw and revert.
The 68k executable you want to run (from Ambient) should be a mapped drawer by e-uae as a filesystem, right?

EDIT: Startup sequence on 3.9 is modified properly with uae_rcli in placed after LoadWB (and checked as executable under c:)

[ Edited by Cool_amigaN 15.03.2015 - 10:36 ]

I prepared for you adf
You start euae with my adf, then run the script "test", which was lha archive
Run the "test" in the CLI Morphos.
If everything will be fine, it will start euae Preferences from the WB1.3
file.lha

Tested, it worked :) Now what?

By the way, just to clarify, in the .conf file I should:
1) Mount the AOS 3.9 installation like this "filesystem=rw,Workbench:sys:emulation/e-uae/HardDisks/aos" (NOT an hdf)
2) Mount Ambient's drawer where my 68k exetubale I want to run is, like this: "filesystem=rw,Workbench:sys:emulation/e-uae/HardDisks/ppaint"
Then right click 68k ppaint executable under Ambient and select "Run in UAE". That should load 3.9 and then automatically call the 68k ppaint executable. Do I get it right?

Also, a slightly different question, I want to mount a CD under 3.1 but want to assign the name of the CD I insert automatically (i.e. I want to display T0 if I insert T-Zer0 cd). I have added in my uaerc the following line "filesystem2=ro,CD0:CD0:CD0:,0", but that mounts my physical CD and displays always "CD" in 3.1, therefore the games don't actually recognise that they runs rom their actual CD (CD behaves just like a mount drawer). My 3.9 installation does it autocmatically but II need it under 3.1. because it's more lightweight whereas I use 3.9 only for uae Picasso modes (which is somewhat slower, especially for games).
How will I do it? I should mess directly with 3.1. adding a device? Actually I haven't a CD drive in my A1200 so, I never went into this kind of trouble before..

It is easy

add to config euae
scsi=true

Now you can use uaescsi.device for cdrom