AWEUTIL.COM divides by zero \ VOGONS

AWEUTIL.COM divides by zero

Topic actions

Post a reply

First post, by moog

Posted on 2022-03-08, 01:29

moog Offline

Rank Newbie

Rank: Newbie
Posts: 96
Joined: 2020-10-15, 13:35
Location: Kashubia

So I tried to load a huge soundfont. I've first taken https://github.com/wrightflyer/SF2_SoundFonts … Masterpiece.sf2 and converted it to .sbk with Awave Studio. It checks out, it's 29,282,950 bytes large, will fit real snug into the DRAM of a fully upgraded AWE64 Gold - which has 29,360,128 bytes of memory.

Some time after trying to load it however, I got this error:
Interrupt divide by zero, stack:
4E7D 2BE2 0206 FF5C 510D 0004 5EA8 0002 0005 0000 0005 0008 FF80

This comes from AWEUTIL.COM version 1.35 from the driver CD. Anyone got any clues what could have gone wrong? I've replaced the stock SYNTHGM.SBK with this newly converted file.

Audigy 2 ZS in FreeDOS
LinLin adapter documentation
+ various capacitor list threads

Reply 1 of 3, by Jo22

Posted on 2022-03-08, 22:18

Jo22 Offline

Rank l33t++

Rank: l33t++
Posts: 9609
Joined: 2009-12-13, 07:06
Location: Europe

"Divide by zero" happens with a few old Turbo Pascal programs when running on PCs in the ~150-233 MHz range and up.

Anyway, that's likely not the issue here.
It just came to mind. A patcher exists for such programs, also.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 2 of 3, by jmarsh

Posted on 2022-03-09, 01:15

jmarsh Offline

Rank Oldbie

Rank: Oldbie
Posts: 1363
Joined: 2014-01-04, 09:17

"Divide by zero" is interrupt 0. Often programs that end up here haven't actually triggered a division error, but accidentally perform an indirect jump to address 0 due to stack/memory corruption.

Reply 3 of 3, by FreddyV

Posted on 2022-03-09, 12:53

FreddyV Offline

Rank Oldbie

Rank: Oldbie
Posts: 756
Joined: 2019-04-08, 11:58

Jo22 wrote on 2022-03-08, 22:18:

"Divide by zero" happens with a few old Turbo Pascal programs when running on PCs in the ~150-233 MHz range and up.

Anyway, that's likely not the issue here.
It just came to mind. A patcher exists for such programs, also.

This kind of problem can happens for other program, with faster machines.

Go to top of page Go to top of page

Back to Sound

Main menu

Common searches