Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Kin-Hell on January 15, 2008, 05:02:54 PM
-
Are there any OS4.0 Classic updates available from these guys yet?
Hyperion entertainment (http://hyperion-entertainment.biz:8080/amiga)
-
OS4 Classic owner here (Cyberstorm), regged with Hyperion and no I know of no updates at all.
(No folder under the download section or anything)
-
I have not even installed mine yet..
-
Oli_hd wrote:
OS4 Classic owner here (Cyberstorm), regged with Hyperion and no I know of no updates at all.
(No folder under the download section or anything)
Hmm. I just can NOT get my A4KT to go online without locking up. Well...I did once & googled "hello" to proove I was on line. Then, after shutting down & rebooting & dragging the Voodoo Monitor to Devs/Monitors, the Miggy locks up when launching IBrowse. From this reboot, the miggy NEVER boots again. No output on the PIV or the Voodoo. The only work-around to boot the miggy under OS4 again is to boot with no startup-sequence, load WB & shut the shell; Go into Internet Prefs & delete the setting that once worked.
The only one time my miggy went online was for Installing as an AGA only machine & not Voodoo, which is a 5500 btw. Mediator's window is set to 512Mb. I have tried to re-install as AGA several times since & can not replicate my sucess in searching hello via google.
This would perhaps suggest DMA issues!
All round, I'm pretty pi$$ed about it.
Another anomally is when Installing to a freshly formatted & empty partition, you get asked if you want to overwrite Font files @ around 7% completion of the install process.
I would consider this acceptable of an OS that was in Beta stage....but NOT Final.
-
This is post copy/paste from Amigans.net
autor : Rogue
"Update on this one:
After I got the new case it turned out that my BlizzardPPC was dying - it would sometimes not initialize at all. I got a replacement two days ago.
The good news is that I've been able to fix the graphics trashing issue. I have also added support for the later Mediator models.
There is apparently another issue with SoundBlaster PCI cards not being set up correctly. Although the drivers don't work because of lack of DMA I intend to fix this since it might affect other cards as well. There is also one other thing that I need to add which.. well... more on that later.
We're putting together a few other things now that should go into a small update, like a fixed RTL 8029 driver. Hopefully this update will then be released later this month."
http://www.amigans.net/modules/newbb/viewtopic.php?topic_id=1426&viewmode=flat&order=ASC&type=&mode=0&start=40
-
VooDoo wrote:
This is post copy/paste from Amigans.net
autor : Rogue
"Update on this one:
After I got the new case it turned out that my BlizzardPPC was dying - it would sometimes not initialize at all. I got a replacement two days ago.
The good news is that I've been able to fix the graphics trashing issue. I have also added support for the later Mediator models.
There is apparently another issue with SoundBlaster PCI cards not being set up correctly. Although the drivers don't work because of lack of DMA I intend to fix this since it might affect other cards as well. There is also one other thing that I need to add which.. well... more on that later.
We're putting together a few other things now that should go into a small update, like a fixed RTL 8029 driver. Hopefully this update will then be released later this month."
http://www.amigans.net/modules/newbb/viewtopic.php?topic_id=1426&viewmode=flat&order=ASC&type=&mode=0&start=40
Er....604e is probably very different to 603e Blizzrds.
I have 128Mb of 60ns Ram on my 233 604e. it MUST be set to 70ns or the miggy will NOT install OS4.0 Classic. Nor will it boot once installed @ 70ns & then changed to 60ns.
I have a 550W PSU feeding my A4KT which is more than enough juice. Chuck a 604e in a Desktop on it's standard 150W supply & forget being stable @ 60ns. The hotter the A4KD gets, the more crashes you see. I run 60ns ram timings on A4KT ram, PPC ram & Z3 Ram under OS3.9 without any issues what so ever. We know OS 4.0 uses a different memory addressing to previous OS'es, but then when you have to turn off your PPC's Memory management unit, you kinda realise that DMA, which Elbox never got right either, is gunno be a pile of trash.
Right now, I'm £60.00 lighter & have hardware that doesn't function correctly & Hyperion haven't even responded since my mail to them 7 days ago.
I'm pi$$ed about this right now, but only to the extent of laughing about it. Quite sad tbh! :lol:
The install I have done is without ANY Zorro cards installed, so Z3 issues are totally out of the equation. Perhaps I need to remove the Picasso IV & try again. I hope I dont have to eat my shorts about it. I'll have to sit in petrol for a week to get em off! :-D
-
Well, I hope they release the driver for the SCSI Controller inthe BlizzardPPC... it's a shame to install it and run it from dead slow IDE...
D.
-
Dragster wrote:
Well, I hope they release the driver for the SCSI Controller inthe BlizzardPPC... it's a shame to install it and run it from dead slow IDE...
D.
IDE works in the A4KD & the A4KT, but the SCSI on the A4KT does not. It's a 40 minute job installing OS4 using an IDE Pioneer DVD 120S device. Only today, I recieved a couple of 50 - 68 way adapaters so I can try my SCSI devices on the CSPPC SCSI III header. I will be making notes & not holding my breath at the same time!
Sorry you A1200 users...I have changed this Threads Title accordingly. Things are complicated enough.
If you are an A1200 User on OS4, please PM me if you feel you have some Info that you feel relevant & keep this thread for 604e Big Box users only.
No offence intended & thanks for your co-operation! :-)
-
hehe.. it's ok, I'm an OS4 604e user too, I have an A4K with CSPPC :-) Anyway, your question was about any OS 4 update for classics... and so far, there's none. We'll see in the near future...
cheers
D.
-
Dragster wrote:
hehe.. it's ok, I'm an OS4 604e user too, I have an A4K with CSPPC :-) Anyway, your question was about any OS 4 update for classics... and so far, there's none. We'll see in the near future...
cheers
D.
So Dragster, ..... Talk to me!
You can see my sig so you know my Config & the Z3 is out but the PicassoIV is still in. I'm gunno leave just a Mediator based A4KT with Voodoo & Ethernet & see what I get.
Can you post your spec please?
Cheers bud! :-)
*edit, I am using an A4KT with Mediator. I can run G-Rex A4KD and/or A4KD X-Surf here. ;)
-
@Kin-Hell
Hehe.. that's a nice setup. Now that we're talking OS4 here, mediator/voodoo is a good choice as there's not much point in using the PIV since you won't be able to run whdload games for example to take advantage of the PIV's scandoubler (unless you have a dual boot setup...but you won't sacrifice VooDoo's performance for some games huh?), in terms of only video capabilities, the VooDoo is way better, of course... (more video ram, gpu..etc).
My A4K specs:
Amiga 4000 Motherboard Revision B, CSPPC 060/50, 604e/233. 128MB RAm + 16 MB RAM on motherboard.
UWSCSI HD (36 GB).
Ariadne II Ethernet.
PicassoIV GFX board with Pablo, Paloma and Concierto Modules.
Dual boot setup with OS 3.9BB2 on the other side.
19" Daewoo CRT Monitor.. (yeah, I know I should change this for a modern LCD...sometime I will)
Soon I hope: A Deneb ZIII/USB 2.0 board.
Cheers. (with some mexican beer if you don't mind...)
D.
-
Dragster wrote:
@Kin-Hell
Hehe.. that's a nice setup. Now that we're talking OS4 here, mediator/voodoo is a good choice as there's not much point in using the PIV since you won't be able to run whdload games for example to take advantage of the PIV's scandoubler (unless you have a dual boot setup...but you won't sacrifice VooDoo's performance for some games huh?), in terms of only video capabilities, the VooDoo is way better, of course... (more video ram, gpu..etc).
My A4K specs:
Amiga 4000 Motherboard Revision B, CSPPC 060/50, 604e/233. 128MB RAm + 16 MB RAM on motherboard.
UWSCSI HD (36 GB).
Ariadne II Ethernet.
PicassoIV GFX board with Pablo, Paloma and Concierto Modules.
Dual boot setup with OS 3.9BB2 on the other side.
19" Daewoo CRT Monitor.. (yeah, I know I should change this for a modern LCD...sometime I will)
Soon I hope: A Deneb ZIII/USB 2.0 board.
Cheers. (with some mexican beer if you don't mind...)
D.
No wories at all m8y....I reckon if the PicassoIV is out of the equation,....everything is gunno be fine on Mediator! I have seen such BS with forcing VGA @ 31Khz whilst using a PIV, to realise the OS4.0 Setup seems to sufer the same BS when in the Early starup screens. Forcing 31Khz using Picasso96 or CyberGraphX 4 seems to totally f'k up the native Early start-up screens. I'm sure there is a link here & it's all down to DMA not being right thro' the Mediator when used with Zorro. I saw the same crap trying to use a Buddha card with the mediator.
Promise to get back in here sometime in the next 24 hrs.
Meantime, have a Mexican Beer for me & I'll sink a couple more Jack Daniels for ya. :-D
-
@Kin-Hell
I have 128Mb of 60ns Ram on my 233 604e. it MUST be set to 70ns or the miggy will NOT install OS4.0 Classic. Nor will it boot once installed @ 70ns & then changed to 60ns.
I have the same CSPPC card and it boots fine irrespective of being set at 60ns, 70ns.
I have a 550W PSU feeding my A4KT which is more than enough juice. Chuck a 604e in a Desktop on it's standard 150W supply & forget being stable @ 60ns.
Again the 604e runs perfectly stable at 60ns in both my 4000D and A4KT.
The hotter the A4KD gets, the more crashes you see. I run 60ns ram timings on A4KT ram, PPC ram & Z3 Ram under OS3.9 without any issues what so ever. We know OS 4.0 uses a different memory addressing to previous OS'es, but then when you have to turn off your PPC's Memory management unit, you kinda realise that DMA, which Elbox never got right either, is gunno be a pile of trash.
I notice your signature suggests you might be running your 68k overclocked @ 80Mhz? I just ask because AFAIK overclocking the 68k also overclocks the CSPPC memory. I seem to recall this was the reason why when I sent a CSPPC to Amigacentre last year the maximum he could overclock safely to was 64Mhz, anymore caused stability problems whilst stressbenching under OS 3.9, OS4 and could break SCSI support.
Right now, I'm £60.00 lighter & have hardware that doesn't function correctly & Hyperion haven't even responded since my mail to them 7 days ago.
Maybe your not using your hardware as it was intended :idea:
-
Akiko wrote:
@Kin-Hell
I have 128Mb of 60ns Ram on my 233 604e. it MUST be set to 70ns or the miggy will NOT install OS4.0 Classic. Nor will it boot once installed @ 70ns & then changed to 60ns.
I have the same CSPPC card and it boots fine irrespective of being set at 60ns, 70ns.
I have a 550W PSU feeding my A4KT which is more than enough juice. Chuck a 604e in a Desktop on it's standard 150W supply & forget being stable @ 60ns.
Again the 604e runs perfectly stable at 60ns in both my 4000D and A4KT.
The hotter the A4KD gets, the more crashes you see. I run 60ns ram timings on A4KT ram, PPC ram & Z3 Ram under OS3.9 without any issues what so ever. We know OS 4.0 uses a different memory addressing to previous OS'es, but then when you have to turn off your PPC's Memory management unit, you kinda realise that DMA, which Elbox never got right either, is gunno be a pile of trash.
I notice your signature suggests you might be running your 68k overclocked @ 80Mhz? I just ask because AFAIK overclocking the 68k also overclocks the CSPPC memory. I seem to recall this was the reason why when I sent a CSPPC to Amigacentre last year the maximum he could overclock safely to was 64Mhz, anymore caused stability problems whilst stressbenching under OS 3.9, OS4 and could break SCSI support.
Right now, I'm £60.00 lighter & have hardware that doesn't function correctly & Hyperion haven't even responded since my mail to them 7 days ago.
Maybe your not using your hardware as it was intended :idea:
Without going into your post with too much detail, if you read the Quickstart guide included with OS4.0 Classic, it tells you to set CS PPC cards ram to 60ns. I have to do this otherwise the OS4 install will not boot from install floppy nor will the OS4 install boot once installed @ 70ns & then changed to 60ns in the CSPPC bios.
I also have to add I can choose between 3 PPC cards here, 2 of which are BOG standard & not overclocked. I see the same BS with the other 2 cards from fresh installs. Thereby making my Oveclock utter tosh!
Thanks for adding to the A1200 Blizzard users comments.
I really need to strip the A4KT & Install from there to see where it goes Pear shaped. For me....it's the Mediator & DMA.....
-
Still not sure whats going on here...I need more time!
-
Sorry to jump in so late, but,
I know a guy who won't post here, he has an A3000 with CSPPC, 604@233. He is having the exact same issues with networking. I am not. I have an A3000 with CSPPC, 604@200. I cannot duplicate his/your problem no matter what.
In case you didn't read my other thread, I have 70ns SIMMs. I made sure the setting was 70ns before installing OS4. After installing, OS4 was very crash-happy. For no good reason, I switched my setting to 60ns, and OS4 has been very stable ever since!
-
I am using an amiga4000D with a csppc and mediator setup to (voodoo3 rtl8029) VArio IO card Spider USB PCI soundcard run OS4.
I made a bracket to push down the ppc chip a bit to get it booting this works fine now.
Ibrowse also crashed on me but when I changed the cache folder to ram: to try it is stable now.
It would randomly crash before I changed this setting.
It is rocksolid now.
But must change afew things though:
Scsi harddisk with OS4 still set to Asynchron and so is the yamaha scsi cdrw.
Yamaha cdrw is a bit flaky(ols age?) so gonna change that to ide harddisk.
Using the yamaha to be able to copy cd's with makecd..if that works with os4.
Also printed with the VArio with a HP lasetjet4 works great and fast!
-
Hmm. I just can NOT get my A4KT to go online without locking up. Well...I did once & googled "hello" to proove I was on line. Then, after shutting down & rebooting & dragging the Voodoo Monitor to Devs/Monitors, the Miggy locks up when launching IBrowse.
I think its safe to say that everyone is having trouble of some sort with OS4, I know I am.
The thing that gets me is "not compatiable" hardware means the system wont boot with it in, Im dual booting between 3.9 and 4 at the moment (95% 3.9 5% 4) and loosing my Fastlane is a real pain (I used it for connecting my external DAT drive and Zip drive as well as for the extra 64meg of memory, and dont have a go at the speed, its faster than the motherboard ram) but with it installed OS4 just wont boot.
For some reason you cant have an empty Prometheus installed (Im waiting for a 90 degree slot adaptor to arrive) because it panics with the OS4 kickstart (the power light flashes and then resets then flashes etc)
My IOBlix ethernet card (add-on to the normal ioblix) works 100% of the time under 3.9 and lower but 4.0 it will stay on for a short time and then crash the TCP/IP program which in turn locks all the internet programs up solid.
For some reason I just cant get the OS4 USB stack to see the Thylacine even though the same OS4 stack in 68K code works just fine. (in 3.9) So no USB on the OS4 side even though I have the card.
you get asked if you want to overwrite Font files @ around 7% completion of the install process.
I got that too, but overall the installation process was fast so mehh.
So yeah Im thinking of uninstalling OS4 for a while, see if things get better later but mehh, compatiablilty is a must for the OS yet they seem to come back with "well the original software wasnt designed right and thats the problem" well sorry, if it works from 3.0-3.9 and 4.0 is the only one not working then its OS4's fault.
Oh one note, excluding when connected to the network Ive found OS4 to be stable although thats only running mplayer and dvplayer, specially designed for OS4.
-
@Kin-Hell
i've tryed to understand what system are having trouble with, without success.
Have you problems going online with the XSurf? or ...
-
Framiga wrote:
@Kin-Hell
i've tryed to understand what system are having trouble with, without success.
Have you problems going online with the XSurf? or ...
It's an A4Kt with PicassoIV, Mediator, Voodoo 5500 & 8139 Realtek NIC along with Spider II USB. Cant get the USB to work Either!
@ Everyone else
Thanks for the feedback so far folks. I have a 200Mhz PPC card as well as 2 x 233 PPC cards & I have no sucess with OS4 & the Mediator on any of them! OS3.9 is fine.
Waiting for an 8029 NIC to arrive & try 10Mbit, though I might as well use the X-Surf as bother! :-?
-
Oli_hd wrote:
So yeah Im thinking of uninstalling OS4 for a while, see if things get better later but mehh, compatiablilty is a must for the OS yet they seem to come back with "well the original software wasnt designed right and thats the problem" well sorry, if it works from 3.0-3.9 and 4.0 is the only one not working then its OS4's fault.
I can't comment on the hardware issues, as I don't have the classic version, but which programs aren't working? You can try adding them to the blacklist in the compatibility prefs. That switches off the 68k JIT for that app. I'd assume that apps that access the AGA chipset directly would still work, given that the actual hardware is srill there on the classic.
However, if the program does something naughty like attempt to read/write from the zero page, unallocated memory, or overwrite code, OS4 will stop it and bring up the grim-reaper. Also programs that do things like peek at memory before an AllocVec() to get the size won't work, because this was illegal in the first place, even though it happened to work. Even Commodore said that these programs would break in the next major OS update. These kind of programs would continue to run on OS3.x, and only cause a failure intermittently. Stopping these apps makes the system itself more stable.
BTW, you might want to check out glUAE (http://saimobvq.interfree.it/glUAE/index.html) (also on os4depot (http://os4depot.net/index.php?function=search&tool=simple)). It will allow you to use UAE to run programs that don't work. It's not ideal, but it works. I'm still waiting for someone to integrate OS4's 68k JIT with E-UAE. Hopefully that will be done at some stage.
Hans
-
@Kin-Hell
I don't have a classic OS4 setup so I can't help too much, but I do have OS4 on an A-one.
Let's see if I have this right: you installed OS4 ok, but have networking troubles causing lockups, after which OS4 won't startup properly. Is this about right?
I'd suggest trying the following:
In s:startup-sequence, change this line:
C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)
to
Run >NIL: C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)
The original line will wait until your ethernet card is connected, has an IP address, etc. If you're ethernet driver is not working properly, this can cause it to stop at this point. Adding run means that the startup will continue, even if you can't get connected (unless the machine really freezes).
I'm guessing, that the driver and your ethernet card aren't working together properly. Not being able to startup after IBrowse locks up suggests that the ethernet card ends up in some unknown state and doesn't get reset properly. This would cause addnetinterfaces to just sit there.
BTW, what ethernet card are you using? Your sig only mentions 10/100 ethernet. Hopefully you're not the only one with that card.
I know that this is frustrating, but, with the number of different cards in use on classic Amigas, supporting all of them is a huge undertaking. They're planning to release an update that fixes at least the graphics issues and Mediator LT (or whatever sub-model) problems later this month.
Hans
-
@Kin-Hell
Copy any eth drivers to OS4:Devs/Networks ;-)
-
Cass wrote:
@Kin-Hell
Copy any eth drivers to OS4:Devs/Networks ;-)
Er.....! Which ones, - Iv'e tried just about everything possible.......
Mediator Drivers Installed; Mediator Drivers Not installed; FastEthernet to Devs:Networks; MediatorNet to Devs:Networks; OpenPCI_8139.device to Devs:Networks; Ver 2.1 OpenPci.Library to Sys:Libs; Copied OpenPCI folder to Env:; Even tried an OpenPci.Library from OS4 Depot.
To try the X-Surf, I need to remove the Mediator board from the A4KT, otherwise, when using a Z3 Riser to clear the PCI slots, the X-surf's RJ45 Port is half blanked out by the back of the Case. :roll:
I can not be arsed to try anyomore.
OS4 for classic Amigas....LOL... What a load of Pi$$!
-
maybe going to SYS:Prefs/Internet> Interfaces (double click onto your NIC interface) and tell to the system what driver/device you want use, it could help!
-
Hans_ wrote:
@Kin-Hell
BTW, what ethernet card are you using? Your sig only mentions 10/100 ethernet. Hopefully you're not the only one with that card.
I know that this is frustrating, but, with the number of different cards in use on classic Amigas, supporting all of them is a huge undertaking. They're planning to release an update that fixes at least the graphics issues and Mediator LT (or whatever sub-model) problems later this month.
Hans
I said it was the 8139 Chipset just before your first post above Hans.
It's quite obvious the drivers arn't working correctly because the Miggy locks up everytime I point it to any of the drivers I install. At this point, rebooting the Miggy results in NOTHING, so in order to boot again, I boot with No Startup-sequence, loadWB & close the shell. Then I open Prefs:Networks & Delete the Entry the Wizard tried to set up in the first place. OS4 will then boot.
This is so pathetic, even when trying to use OpenPci.library 2.1 & pointing the Network Wizard to OpenPci_8139.device in Devs:Networks, it tells me it can not use OpenPci v2.x?
Not much point trying your Startup-sequence mod. The card cant find it's own Ass, never mind an IP address over @ my Router!
Time for some more Jack Daniels & time to kick this crap into touch!
-
Framiga wrote:
maybe going to SYS:Prefs/Internet> Interfaces (double click onto your NIC interface) and tell to the system what driver/device you want use, it could help!
Only to get the Miggy Booting again after it fk's itself up! ;-)
-
Kin-Hell wrote:
Not much point trying your Startup-sequence mod. The card cant find it's own Ass, never mind an IP address over @ my Router!
The startup-sequence modification should enable you to bootup to workbench despite the ethernet driver issue.
I've just looked at the OS4 classic compatibility list (http://www.acube-systems.biz/compatibility/), and it lists the 8139 card as unsupported because it requires the Mediator DMA hack. So there's your problem; you're trying to use a card that is known not to work.
If you haven't done so already, you could try installing the 68k Mediator drivers, but you'll have to do that for absolutely every card plugged into your Mediator board. The OS4 native and classic Mediator drivers can't coexist.
Failing that, bug Elbox to write OS4 drivers that use the graphics-card DMA hack.
Hans
EDIT: I wish that we'd thought to look the card up in the compatibility list earlier as it would have saved so much time and frustration.
-
Hans_ wrote:
Kin-Hell wrote:
Not much point trying your Startup-sequence mod. The card cant find it's own Ass, never mind an IP address over @ my Router!
The startup-sequence modification should enable you to bootup to workbench despite the ethernet driver issue.
I've just looked at the OS4 classic compatibility list (http://www.acube-systems.biz/compatibility/), and it lists the 8139 card as unsupported because it requires the Mediator DMA hack. So there's your problem; you're trying to use a card that is known not to work.
If you haven't done so already, you could try installing the 68k Mediator drivers, but you'll have to do that for absolutely every card plugged into your Mediator board. The OS4 native and classic Mediator drivers can't coexist.
Failing that, bug Elbox to write OS4 drivers that use the graphics-card DMA hack.
Hans
EDIT: I wish that we'd thought to look the card up in the compatibility list earlier as it would have saved so much time and frustration.
Yeah Hans... I'm not frustrated in the slightest. Not even about spending £60 on an OS that isn't as useable as Linux.
Thanks for the feedback, I really appreciate it.
I'm using the Mediator 3.10 drivers under OS3.9 with the 8139 card. I am not running a DMA hack as far as I am aware.
Do you have any info about this hack please? The usual searches returned ziltch!
It's quite funny thinking back to when these cards were first released. The PPC chip was suppose to be doing things much much faster whilst running the Native Amiga OS. Here we are now with the PPC running an OS that cant do anything with 68K programs. The Amiga, back in it's hey day could Emulate EVERY platform available.
The Irony of it all. :roll:
-
Kin-Hell wrote:
I'm using the Mediator 3.10 drivers under OS3.9 with the 8139 card. I am not running a DMA hack as far as I am aware.
Do you have any info about this hack please? The usual searches returned ziltch!
You are actually using the DMA hack because it's used by Elbox's Mediator drivers. I can't think of any good resources that explain what happens. Basically, the Mediator board can't DMA to main memory (I can't remember why). So what it does is it reserves some memory on your PCI graphics-card and uses PCI bus-mastering to DMA to memory of the PCI graphics-card. From there it can be copied to main memory. This is a hack as it's working around hardware limitations that prevent it from doing direct DMA. It also requires that you have a graphics-card present.
This means that every card that requires DMA in order to work requires special Mediator board code that differs from the driver used by other systems (e.g., the AmigaOne, whose north-bridge supports DMA to main memory). Basically, this would mean that every PCI card that uses DMA would need two drivers, one for PCI northbridges that support DMA, and a special one specifically for the Mediator boards. It's not a minor change to the drivers.
Hopefully Elbox will support their products and release OS4 versions of their drivers. In the mean time, I've been told that you can use the 68K Mediator drivers you use under OS3.9 on OS4 too, but you have to change ALL your PCI drivers to the 68K Mediator ones. You cannot mix the OS4 native and Mediator drivers. Alternatively, you could look for an 8029 card, which does work (and a bugfix for the driver is coming).
Hans
-
amiga4001 wrote:
I made a bracket to push down the ppc chip a bit to get it booting this works fine now.
The PPC Heatsink & fan should be held on via 2 x clips. On the backside of the PPC board, make sure these 2 x clips are ALL the way through. At the same time, I`d be checking, Cleaning & re-applying some thermal compound to the PPC Heatsink/Core interface. If doing all this means you still have the problem, make sure the whole PPC Cards Edge Connector is seated correctly on the motherboard connector.
Meantime, I`m trying to find out why an Installation of OS4 totally shafted an IBM 10,000 RPM hard drive. Since the re-boot from Installation, which went great including NOT seeing the copy files issue @ 7% (I formatted using long file names) I get a Software Guru screen. I have managed to hot-swap this drive whilst booting from floppy & deleted the installation partition. It`s still a no go here, but I can throw another 6 drives at it yet. Me thinks the drives RDB is Fux0rd!
-
Meantime is now by the by & all drives have healthy RDB`s again after much hot-swapping & tricking the Hard drive into thinking it was the original Hard drive seen by Media Toolbox. I picked up on another thread RE using SFS in order to support Long File Names under OS4, so theoretically, I was right about the RDB being shafted, even if I didn`t know the exact reason why. :-? Now not so sure the Format should allow fux0ring of the RDB in this way. Surely it should say you need to install another File System able to cope with the long filenames or maybe I just mis-interperated the Quick Guide; Though it beats the cr4p out me as to where is the Full Manual??
So far, OS4.0 Classic has installed with a CVPPC card on a PC monitor right from the boot floppy. X-Surf is still a no go despite being plugged directly into a Zorro Slot without the Mediator even being in the same room!
Got lots more playing to do yet, but the hard drives are rcovered at least! :roll: