WinUAE 3.0.0 beta series (was 2.8.2/2.9.0)

[thomas]

Originally Posted by Toni Wilen

Thanks. It is "too long" transfer, 910 blocks which overflows internal buffer. Unfortunately SCSI emulation needs separate buffer but allocating megabytes just for SCSI buffers isn't that optimal. Need to find some better solution..

SCSIEMU HD 0: 28.00.00.05.AB.B0.00.03.8E.00.00.00

I wonder how this can be when MaxTransfer is set to 0x1fe00 (255 blocks). Either cybppc.device consolidates multiple CMD_READ into one SCSI read or the file system (SFS 1.279) ignores MaxTransfer. Or something else

[Toni Wilen]

Originally Posted by thomas

I wonder how this can be when MaxTransfer is set to 0x1fe00 (255 blocks). Either cybppc.device consolidates multiple CMD_READ into one SCSI read or the file system (SFS 1.279) ignores MaxTransfer. Or something else

No idea. Perhaps SFS "detects" that max transfer can be ignored by checking some device attributes or something..

http://www.winuae.net/files/b/winuae.zip has buffer auto-increase added, does it work now? (A2091 autoconfig issue also fixed)

[thomas]

Works + works. Thank you very much.

[AMIGASYSTEM]

Originally Posted by BinoX

I have added this step to my tutorial and credited you in the update section of the first post. I've never noticed that option in that section before, many thanks for pointing it out.

Thanks BINOX I reported all the problems HERE and I will also HERE, also just finished your tutorial will be posted on these forums.

[billt]

Originally Posted by BinoX

I have added this step to my tutorial and credited you in the update section of the first post. I've never noticed that option in that section before, many thanks for pointing it out.

Where can we find your tutorial?

[huepper]

I have setup an A2000 with B2060 and 128 MB accelerator memory, but in workbench fastram will not appear.
Wrong config ? (have changed .bin to .rom also)

[BinoX]

Originally Posted by billt

Where can we find your tutorial?

http://eab.abime.net/showthread.php?t=74776

I didn't have time to do the networking tutorial last night after all... I'm starting work on it now

[Toni Wilen]

Originally Posted by huepper

I have setup an A2000 with B2060 and 128 MB accelerator memory, but in workbench fastram will not appear.
Wrong config ? (have changed .bin to .rom also)

ROM is not properly loaded (I can say it even without log this time!).
You probably forgot to rerun rom scanning after rename.

[BinoX]

Guide updated. Network support and browser installation added.

[Retrofan]

I've been waiting for someone to report any problem, but it seems I'm the only one. I can not boot OS4.1 with the latest betas (black screen forever). The last working is b12. I use the same WinUAE config for all of them, and I always rescan the same roms when I try another beta.

I just want to know if you can boot it with the latest betas.

[FOL]

Originally Posted by Retrofan

I've been waiting for someone to report any problem, but it seems I'm the only one. I can not boot OS4.1 with the latest betas (black screen forever). The last working is b12. I use the same WinUAE config for all of them, and I always rescan the same roms when I try another beta.

I just want to know if you can boot it with the latest betas.

I find that sometimes the config doesnt load correctly and results in PPC flashrom not being set. Gives constant black screen.

[amigafreak68k]

I think he mean black screen after AOS 4 ROM loading... I'd visited this behavior also today, but had no time to do more tests...

[Retrofan]

And now I've tried with b12 and it boots (floppy and Cd), but when I get to format, there is no DH0 there. Perhaps something happened with b13 that changed it (the hdf). I'll keep trying.

[Ami_GFX]

I'm booting the same with B12 and B13. It takes a long time but I get to the OS4.0 desktop.

[MickJT]

I've noticed the last winuae.zip seems to be generating log files that are hundreds of megs in size (at least when using PPC). b13 is OK.

[huepper]

Originally Posted by Toni Wilen

ROM is not properly loaded (I can say it even without log this time!).
You probably forgot to rerun rom scanning after rename.

I have rescanned roms some times.
I can't use fastram or better, b2060 in my config.
If i check early startup, card is not shown.

Other thing is, i load the config, boot into workbench (with workbench3.1 adf) and if i quit (f12 + quit) i get a crash all time.

[ancalimon]

I'm not sure when this started to happen but when I choose "Fullscreen" on my second crt monitor on the left (native Amiga display), mouse gets stuck on the right portion of the screen. I can move the mouse but it randomly won't go further to the left after some point.

[AMIGASYSTEM]

Is it possible to surf the Internet inheriting the connection from the PC, on OS4.0 exits already the ability to connect over WiFi as you do on AROS?

OS 4.0 Classic


Icaros Configuration
WiFi

[Mad-Matt]

Originally Posted by Retrofan

And now I've tried with b12 and it boots (floppy and Cd), but when I get to format, there is no DH0 there. Perhaps something happened with b13 that changed it (the hdf). I'll keep trying.

With beta 13, my OS4.0 is booting, but the ppc emulation s running 100s of times slower than usual. Its slowed considerably in my warpos install as well.

[Toni Wilen]

Originally Posted by huepper

I have rescanned roms some times.
I can't use fastram or better, b2060 in my config.
If i check early startup, card is not shown.

Other thing is, i load the config, boot into workbench (with workbench3.1 adf) and if i quit (f12 + quit) i get a crash all time.

Logs nor dumps are not from any official beta. Do not use winuae.zip unless requested. (Do you really have both rom files? _hi.rom and _lo.rom?)

EDIT: workaround: set ROM panel 2060 path to blank.

To everyone: Stop posting "it does not work reports"!

- if not new feature in this beta series: Must test last official version!
- Do not use winuae.zip unless requsted.
- If feature introduced in previous beta: must test if it worked in previous beta.
- Asking about PPC OS related questions: -> WinUAE PPC thread.

Extra rule since it seems everyone enables CSPPC just because you can and then report about something totally unrelated: Set up standard config (no accelerator boards!) if your problem has nothing to do with PPC.