Bridgeboard emulation (x86 CPU, for example A2286)

[AnnaWu]

Originally Posted by amigasystem

just to understand, if possible, you tell me about what filesystem you installed your os 2.04, thanks

FastFileSystem

[AMIGASYSTEM]

Originally Posted by AnnaWu

FastFileSystem

Thank you Anna, I can now proceed, prepare a compatible HardDisk PC "AT IDE Primary" and I try my system OS2.4 with ENFORCER started in the startup-seuence

[AMIGASYSTEM]

Bene fatto il test:

- OS 2.04/030
- Started ENFORCER successfully (see screenshot)
- Rremoved "SMARTDRV.EXE", "HIMEM.SYS" and "DOS=HIGH" in your config.sys and autoexec.bat
- Everything is fine except for AMOUSE, where did I go wrong?

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Bene fatto il test:

- OS 2.04/030
- Started ENFORCER successfully (see screenshot)
- Rremoved "SMARTDRV.EXE", "HIMEM.SYS" and "DOS=HIGH" in your config.sys and autoexec.bat
- Everything is fine except for AMOUSE, where did I go wrong?

Why 68030? Why Enforcer? (It will be as useless as OFS/FFS difference!) It won't do anything in emulation (Unless you have MMU/prefetch emulation). Do normal debugging: Remove all possible unknown variables, set as basic config as possible first: 68020 (or even 68000). You still haven't explained whats the problem with AMOUSE? Error message? Nothing happens? More information needed. You do see Janus Handler message?

If you run Amiga-side mouse server (PC/Services/MouseServ), does it open requester that says it is already running?

(That enforcer screenshot is totally useless, better start including information that actually matters.. = shows the actual problem, settings and so on. EDIT: Without enough information, we can only guess or ask same questions again and again, not help)

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Why 68030? Why Enforcer?

Because I wanted to test this configuration AnnaWu

Remove all possible unknown variables, set as basic config as possible first: 68020 (or even 68000).

I had already removed any possible unknown variables, command ENFORCED in startup-sequence OS2.4 with the CPU 68000 generates a GURU, with the 68020 (Crash), with the 68030 the comand ENFORCER part it runs perfectly. I am quite experienced in Amiga OS and know well manage the startup-sequence.

You still haven't explained whats the problem with AMOUSE? Error message? Nothing happens? More information needed. You do see Janus Handler message?

Message error "Amiga colud not load Mouse Serv" "A MOUSE not installed"

If you run Amiga-side mouse server (PC/Services/MouseServ), does it open requester that says it is already running?

No, the first double click nothing happens, if you repeat the double-click a request "AMouse is already active". Pretty much the same things that i on OS1.3, AMOUSE where it installs perfectly.

What I do not understand, is because if I change the file system to OFS AMOUSE It installs any CPU, any OS Amiga 2.x e 3.x, any Startup-sequence any if you packed with extra commands.

[AnnaWu]

Originally Posted by AMIGASYSTEM

Bene fatto il test:

- OS 2.04/030
- Started ENFORCER successfully (see screenshot)
- Rremoved "SMARTDRV.EXE", "HIMEM.SYS" and "DOS=HIGH" in your config.sys and autoexec.bat
- Everything is fine except for AMOUSE, where did I go wrong?

Maybe it is a problem with MS-DOS 6.22 and AMouse?
It works for me with MS-DOS 6.0

And yes, it works without Enforcer too.

[Sandro]

Originally Posted by AMIGASYSTEM

Did some testing with the games and I have to say that a good work, successfully tested various Doom although they are a little slow.

a little slow? how many fps ?
which cpu are you using?

[AnnaWu]

@AMIGASYSTEM
Sorry

Mouse driver (AMouse/AMouse3)
Take now care about OFS and FFS.
I think I told you nonsense before.
For me exist a conflict with FFS and the mouse driver(s) too.

[AMIGASYSTEM]

Hello Anna, and thanks again for ifile you sent me, made a little test, and I found that the problem was not MS-DOS 6.22 (see screenshot), without removing "SMARTDRV.EXE", "HIMEM.SYS" and "DOS = HIGH" in your config.sys and autoexec.bat, Also settings WinUAE going well. My problem was in OS 2.4, not the startup-sequence, now slowly make various comparisons and I look to find the cause of the failure.

[Toni Wilen]

Finally actual error message was included! Took long enough.. (Instead of "not working")

Usual requirement: attach/email/whatever the non-working HDF.

[Seiya]

i'd like to say that on Desktop keyboard, "END+F9" doesn't work..

[AMIGASYSTEM]

Originally Posted by AnnaWu

@AMIGASYSTEM
Sorry

Mouse driver (AMouse/AMouse3)
Take now care about OFS and FFS.
I think I told you nonsense before.
For me exist a conflict with FFS and the mouse driver(s) too.

In fact the difference between your OS and my is precisely that, maybe I was right

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Finally actual error message was included! Took long enough.. (Instead of "not working")

Usual requirement: attach/email/whatever the non-working HDF.

As Toni said that "not working" I am often given da Google Translator by, the Italian, has many more synonyms and idioms, see screenshot

Sipegato as my last intervention the problem was just the filesystem FFS, Anna now as I understand it confirms. With OFS all the OS tested were capable of initiating AMOUSE.

[Toni Wilen]

"Not working" means: include FULL error message, describe what happens in detail. Don't be lazy and only say "it does not work".

It still 100% guaranteed real problem is not FFS. Do you still think every bridgeboard owner only used OFS. It would be 100% impossible! Real cause is something else. It needs to be found.

Other tests that needs to be done:

Copy OFS HDF contents to empty FFS: Does it now work?
Copy FFS HDF contents to directory filesystem: Does it now work?

[AMIGASYSTEM]

Ok Toni delete the word "working" from my little English vocabulary

About FFS I agree with you, I've done hundreds of tests with many variations and with all OS 2.x e 3.x always a negative outcome. Probably there will be a way, we see with the help of everyone to find the right care .

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Other tests that needs to be done:

Copy OFS HDF contents to empty FFS: Does it now work?

I'll do the test

Copy FFS HDF contents to directory filesystem: Does it now work?

directory filesystem:? I did not understand

Copy FFS HDF contents to empty OFS: Yes, work with OS2.x and OS3.x

[Toni Wilen]

Originally Posted by AMIGASYSTEM

directory filesystem:? I did not understand

Host directory mounted as a harddrive. ("Add Directory or Archive" button)
I have done all tests using directory harddrives, hardfiles are annoying to use.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Host directory mounted as a harddrive. ("Add Directory or Archive" button)

Ok i understand, I'll try this

I have done all tests using directory harddrives, hardfiles are annoying to use.

I'm much better with hardfiles

[AnnaWu]

Originally Posted by Toni Wilen

Host directory mounted as a harddrive. ("Add Directory or Archive" button)
I have done all tests using directory harddrives, hardfiles are annoying to use.

How can I detect the used FileSystem?

[Arnie]

I have made a fresh Install of Janus to my A3000 config, installed Dos to the Janus hardfile (31mb) and everything is working. I wanted to Install Windows 3.0 to test the mouse but first I needed to add the x86 RTG. This is the part that is refusing to work. Adding RTG and setting the PC Prefs results in a black screen with lines (SIC).

EDIT: Trying to switch back to non RTG by changing PCPrefs doesn't work unless the RTG is disabled in the config.