@AMIGASYSTEMS
If you try a second time it states no boot sector for me.

No, if you quit WinUAE and then run again revise it, in some cases it is necessary to make a PCREset, I also tried the 512, could partition, but then FDISK does not save the MBR Now you go to dinner otherwise the wife who feels

I've tried using the a2286 with several of the bios images both with and without x86 video rtg and the workbench freezes (but not all of WinUAE) every time I launch PCPrefs from the PCInstall dms file found on amiga.resource.cx. Anyone have any suggestions?

Do not use old DOS hardfiles, they must be created from scratch. Most previous bridgeboard configurations used incorrect IDE byte swapping.

- XTIDE "fake" 8-bit accesses really work now.
- $DC000 base address is now protected from Amiga-side modifications ($DC000 conflicts with $DC0000-DCFFFF Amiga/PC communication space but it seems only beginning is actually used, use only if any other XTIDE address does not work = Boot messages don't appear)

When you get this working to your satisfaction, would you be willing to write up a short guide on how we set up the bridgeboard step by step?

Thanks so much!

Done on the fly a VideoTube Tutorials, I hope it is understandable, the video shows the different configurations and the start of the two operating systems. For a new installation of MS-DOS you just insert the floppy in the position shown in the video and start the 386 from the floppy MS-DOS 6.22, of course everything can be improved, used in the video Amiga OS 2.1 but you can do the same with any OS from Amiga OS 1.3 to 3.9.

Do not use old DOS hardfiles, they must be created from scratch. Most previous bridgeboard configurations used incorrect IDE byte swapping.

- XTIDE "fake" 8-bit accesses really work now.
- $DC000 base address is now protected from Amiga-side modifications ($DC000 conflicts with $DC0000-DCFFFF Amiga/PC communication space but it seems only beginning is actually used, use only if any other XTIDE address does not work = Boot messages don't appear)

Was the new WinUAE version tested with the A1060 Sidecar/A2088(T) expansion and the installed Janus 2.1 driver?

Made some small test on 386, I noticed that even with some 386 games like Prince of Persia and Zool not leave for strange reasons, not being an expert in MS-DOS can not understand the reasons. I tested the same games on the DOSBox Emulator successfully, they start games normally.

Another thing I noticed and that the MS-DOS can not enter ASCII characters such as Alt + 126 (useful for filenames truncated) instead of ASCII characters out other strange characters. Out of curiosity I run the System Information utility, here are the results of screenshots

Made some small test on 386, I noticed that even with some 386 games like Prince of Persia and Zool not leave for strange reasons, not being an expert in MS-DOS can not understand the reasons. I tested the same games on the DOSBox Emulator successfully, they start games normally.

Another thing I noticed and that the MS-DOS can not enter ASCII characters such as Alt + 126 (useful for filenames truncated) instead of ASCII characters out other strange characters. Out of curiosity I run the System Information utility, here are the results of screenshots