What do think of OS4.0 Classic Version?

[TetiSoft]

lurkist wrote:
I'm having similar problems to everyone else with my 3com card, despite the first option in the "new connection" menu being for said hardware.  I'm confused as to how they expect any of those options to work, since the DEVS/Networks folder (and its storage counterpart) have virtually nothing in them.

IIRC there were reports that the 3com589.device works,
and reports stating the opposite. The card is not on the
OS4 compatibility list. cnet.device is listed there as
working. OS4 does not include third-party network drivers
but offers you a list in the "New Connection" wizard.
For a basic ethernet network with a router to the outer
world, you can use Prefs/Internet instead of Internet/New Connection which is more for dialup and PPP stuff.

[TetiSoft]

A4000_Mad wrote:
Yeah I've got problems with DV Player as well. I've got sound but no picture. However, if I click on the player and nudge it around a bit, the picture comes and goes while I'm moving it. But whenever the player is still there's no picture at all (it's just black) :-?

You can try to use the NOOVERLAY tooltype of DVPlayer,
on a PicassoIV this fixes the problem.

[TetiSoft]

AmigaMance wrote:
@motorollin

AGA screenmodes are generated by the custom chips, which only have access to Chip RAM.

 I'm sure you have heard of FBlit before, haven't you? Classic OS users benefits from its function for more than a decade. A supposly much more advance OS like OS4 should have this feature intergraded.

FBlit is a third-party 68k patch for OS3.
Its likely that it is not compatible to everything
which runs under OS3, then you have the option to not
use it. If it would be integrated in OS4 it could not be
disabled, reducing backwards compatibility.

IMHO it should be possible to create an OS4 compatible
version of FBlit. But for OS4 a gfx board is recommended
anyway so it doesnt matter much.

[TetiSoft]

A4000_Mad wrote:
I've just had a go at setting up a hard drive that can boot into either OS3.9 or OS4 :-)

My findings........

1. I could *not* boot into OS4 then do a soft reset while keeping both mouse buttons held down to get the the 'Amiga Early Startup Control' and then choose to boot into OS3.9 partition. The result was a red screen (ROM error alert)

See Documentation/C/BootLoader.doc, near the end,
the part that begins with "Remember that the OS 4 kickstart is sticky".

2. I could *not* boot into OS3.9 then do a soft reset while keeping both mouse buttons held down to get the the 'Amiga Early Startup Control' and then choose to boot into OS4 partition. The result was a red screen (ROM error alert)

See Documentation/C/BootLoader.doc, near the start,
the part that begins with "The program "BootLoader" needs to be executed once".

Hint: BootLoader causes a reboot so you may have to enter
bootmenu twice.

3. With OS4 set as the partition with highest boot priority and doing a cold boot, I could *not* successfully go into the 'Amiga Early Startup Control' and choose to go into OS3.9 (it would just go into OS4 anyway)

See your OS3 documentation. I guess you missed that the
typical OS3 installation does a reboot during boot caused
by SetPatch, ergo you have to enter bootmenu twice.

4. I *was* able to boot into OS3.9, use 'HDToolBox' to give the OS4 partition a higher boot priority and do a soft reset into OS4.  

5. I was *not* able to boot into OS4, use 'Media Toolbox' to give the OS3.9 partition a higher boot priority and do a soft reset into OS3.9.  The result was a red screen (ROM error alert)

See Documentation/C/BootLoader.doc, near the end,
the part that begins with "Remember that the OS 4 kickstart is sticky".

Hint: Ctrl-Alt-Alt leaves OS4.

Conclusion:-

'Media Toolbox' and 'HDToolBox' seem to be an answer at this time :pint:

Read Documentation/Kickstart/bootmenu.doc.