What copy did you download? The 360kb 5,25" version or the 720kb 3,5" version?

You configure it the same way as you configured the hard drive. You set the correct drive type in 86Box settings, then set the same drive type in CMOS. Obviously the drive type needs to be supported by the machine you're emulating (in your case, it supports just about all standard types, so no worries), and the disk images you're using need to be compatible with this drive.

In case you're not familiar with floppy disk formats and drives, I recommend you look up 3.5" and 5.25" drives and disks on Google to get an idea.

I downloaded the 720kb 3.5 version of Windows/386

Your drive A must be 720kb 3,5" and your drive B must be 360kb 5,25"

I set the drive A to the 720kb 3.5 option and I got an error. Here is the error: General Failure error reading drive A. Is there a way to fix this?

Set the drive options in the CMOS.

If you've inserted the disk on drive B, it would say that.
Edit: Also, is the drive set to 720K/1.44M in the CMOS so that it matches the 86box settings?

It won't let me change the option of the floppy drive.

You need to press pageup or pagedown from your keyboard (at least in the ami386dx).

I installed it but when I type in win386, it freezes on the boot screen. Is there a fix for this?

Hmm, you've assigned 8MB of memory, haven't you? Also, DOS version? What type of freeze? Something about the DOS version?

I am using 8MB of memory. The version of DOS I am using is MS-DOS 3.31. I don't know what type of freeze it is.

Mind offering a screenshot (not from a camera) of the freeze?

Here is a screenshot of the freeze: https://www.betaarchive.com/imageupload ... .58167.PNG

Well, one issue that may or may not be related to this freeze, but will be an issue of its own eventually, is the fact that you're using a PS/2 mouse on a board that doesn't support PS/2. As I've said in one of my previous posts, switch to Microsoft serial mouse (and reinstall Windows with the appropriate mouse driver selected).

Also, in case you didn't do this: you should allow setup to modify your AUTOEXEC.BAT and CONFIG.SYS files, and MEMSET to do its thing.

I don't think it is related to this freeze and I allowed setup to modify the autoexec.bat and config.sys files and I ran MEMSET and it freezes at the boot screen