Floppy & Network errors

[Saghalie]

I'm having issues with getting the emulation to recognize the floppy and the network card.

The issue started with 3.2.2 - and it only happens when using the AmigaOS 4.1FE (PPC) OS.

When using AmigaForever though, I don't have a problem - it all works fine.

Also, any floppies that I inserted and showed up "df0:unitialized" now do not work in any other emulated configuration. I have created new floppies through the emulation and those do not work as well. I have tried to diskcopy as well in a different emulation and format a "bad" disk and both give me errors that it cannot format the disk due to an error in block 0 or 880.

The network just will not work. It gives me a "No route to host" error if the device installs - but now after many reboots, it does not recognize that the a2065.device or rtl8029.device can be opend (on port 0)

As always: files attached.

Regards,

Saghalie - (Wawa Koppa Saghalie)
(Talks to the Sky)

[Toni Wilen]

Attached config has PCI network card without any PCI bridge.

[Saghalie]

Originally Posted by Toni Wilen

Attached config has PCI network card without any PCI bridge.

Sorry it took so long getting back to you. I was trying all configurations with the PCI bridge. None of them worked.

Here is the output of one of them.

----
Any ideas on the floppy issue? Do you need anything from me?
I did boot up in a known working configuration and used QBTools to fix one
of the floppy disks but when I inserted in to this configuration I still got the
bad block 880 error.

Regards,

Saghalie

[Saghalie]

Network is up and running. Guess I didn't do "all" the configs. Anyway it sure as H*** doesn't like to share the connection with the PC - locked me all up until a download was completed...

Still have the floppy issue though. I can do a disk fix on them in a different emulation but when I load up 4.1FE it gives me the disk error at 880 error.

Regards,

Saghalie

[Toni Wilen]

Originally Posted by Saghalie

Network is up and running. Guess I didn't do "all" the configs. Anyway it sure as H*** doesn't like to share the connection with the PC - locked me all up until a download was completed...

It could be simple out of memory situation (128M is not much and Z3 swap memory is unreliable in OS4). Try something simpler first. (Any kind of not guaranteed, can't be 100% duplicate, requires extra programs, emulation problem when running OS4 = will be ignored)

Still have the floppy issue though. I can do a disk fix on them in a different emulation but when I load up 4.1FE it gives me the disk error at 880 error.

Can't duplicate.

[Saghalie]

in order for me to get the network working I have to add these lines to the .uae config:

prometheus_rom_file=:ENABLED
mediator_rom_file=:ENABLED
mediator_rom_options=subtype=1200,fulldma

If I remove the prometheus_rom_file line, the network will not work. I haven't tried vice versa yet.

I'm also noticing that I have to go in to the config file and manually remove items in order for my system to work.

I'm not sure if it's a PC problem or something going on with WinUAE.

Regards,

Saghalie

[Toni Wilen]

You have CyberStormPPC setup. Which is for A4000. Then you enable Mediator 1200. Which is not accepted by OS4. Not very surprising.

Don't enable things blindly, check hardware specs first.

[Saghalie]

Had to do it this way. No other config would work.

[Toni Wilen]

Originally Posted by Saghalie

Had to do it this way. No other config would work.

Then you are doing something wrong. Mediator 4000 does work.

EDIT: Attach your config and log with Mediator 4000 only, if it still refuses to work.

[Saghalie]

Originally Posted by Toni Wilen

Then you are doing something wrong. Mediator 4000 does work.

EDIT: Attach your config and log with Mediator 4000 only, if it still refuses to work.

It's a moot point now. My raid array crashed and I had to install new hard drive and disable the raid array until I can get new hard drives. ... got the system up and running and don't have any issues. Everything seems to be working now. Floppies are even working.

I can only assume that there was something going on with the disks as they were crashing.

Thanks for your time.

Regards,

Saghalie.