Maybe you need another Dosbox Build..

When i installed Win95 on Dosbox, i get some errors during installation too. (not the same errors as you)

Ended up with Dosbox Daum January 2014 as the best for me.
But i use Windows as Host-System.

It also depends on which version of Win95 you try to install: Retail, B or C.

I used Win95. But most Installation-Guides say you should use Win95(a)

Use a virtual machine that supports Windows 95.

Neverhood works with Scummvm.

Yeah, you shouldn't use Dosbox to run Windows 9x. But if you try, use my build of the latest source...

kxonline wrote:

I then get an error message that reads, 'A fatal exception OE has occurred at 0137:BFF7F21D. The current application will be terminated.'
I will provide screenshots of the startup and error screens.

Does anyone have any idea on how to fix this? Please share!

The disk is damaged.

https://support.microsoft.com/en-us/kb/176446

This behavior can occur if you install a program that creates a shortcut for a Web address, and the shortcut is associated with an icon that does not exist. This icon is not the default icon associated with a shortcut for a Web address. For example, if a program installs a shortcut for a Web address in your Favorites folder, it is assigned a company logo icon, but the icon file may not be installed. When you start your computer, Windows 95 reads the Favorites folder, cannot find the icon file for the shortcut, and generates the error message.

Note that this problem occurs only if you are not running the Windows Desktop Update. This behavior also occurs in Safe mode.

A more generic 0137
https://support.microsoft.com/en-us/kb/179347

This behavior can occur if the Advapi32.dll file located in the Windows\System folder is missing or damaged.

Wait a minute.

kxonline wrote:

Command prompts are as follows (on Mac): mount C: ~/DOS (my folder containing the W95 img) C: imgmount A: C:/W95.img boot W95.im […]
Show full quote

Command prompts are as follows (on Mac):
mount C: ~/DOS (my folder containing the W95 img)
C:
imgmount A: C:/W95.img
boot W95.img

This doesn't seem like it should work at all.

You should use
imgmount c ~/DOS/W95.img
boot -l c

Jorpho wrote:

Wait a minute. […]
Show full quote

Wait a minute.

kxonline wrote:

Command prompts are as follows (on Mac): mount C: ~/DOS (my folder containing the W95 img) C: imgmount A: C:/W95.img boot W95.im […]
Show full quote

Command prompts are as follows (on Mac):
mount C: ~/DOS (my folder containing the W95 img)
C:
imgmount A: C:/W95.img
boot W95.img

This doesn't seem like it should work at all.

You should use
imgmount c ~/DOS/W95.img
boot -l c

Wow, didn't know that this works already that easy!
DOSBox has quite evolved since I tried the last time..

This is how I used to boot an image file in DOSBox:

[autoexec]
# Lines in this section will be run at startup.
mount d: c:\dbox
imgmount c d:\c_dosbox.img -size 512,63,16,1015 -fs fat
boot -l c

Actually, I am a little surprised that it autodetects the size parameters. But the drive C is the important thing, I think.

I was actually poking at that the other day and I'm not sure how it works. If you look at the screenshots above, it says "Booting from drive A", but scandisk is clearly checking drive C – and drive C (mounted as ~/DOS) shouldn't be accessible at all after using the "boot" command. So does that mean DOSBox or Windows 95 automagically reassigned the drive letter, or at least tried to?

I see, that's an interesting question. I have to admit, I never tried to boot an hard disk image as "A:".
Perhaps "Booting from drive A:" only refers solely to the mounting point ("Drive A is mounted as .. W95-3.img" ?

Edi:t Just checked, the image is handled as drive "C".