I get the following exception every time I loose the game (Windows 7 64bit, Oracle Java 7 64bit): I'll have to try it again with o/c to 3ghz. Uses more than 50% of my 2.4ghz quad core. If the game runs too fast try a fixed cycles amount in DOSBox's options.ĬPUID at _Interrupt(CPU.java:1093)Īt _Exception(CPU.java:1019)Īt _Interrupt(CPU.java Īt _Interrupt(CPU.java:1093)Īt _Interrupt(CPU.java:1093) Reply 181 of 203, by danoon VBE Bios $Id: vbe.c,v 1.60 2 07:47:21 vruppert Exp $ĭOSBox switched to max cycles, because of the setting: cycles=auto. IDE: Adding IDE controller to port 0x170/%03x IRQ 886 IDE: Adding IDE controller to port 0x1f0/%03x IRQ 1014 Mounted FAT volume is FAT12 with 2863 clusters Parsing command line: SET BLASTER=A220 I7 D1 H5 T6 Special file open command 80 file Z:\AUTOEXEC.BAT HARDWARE_Init not finished yet: NO SCREEN SHOTS DOSBox version 0.74.27Ĭopyright 2002-2010 DOSBox Team, published under GNU GPL.ĬONFIG:Loading primary settings from config ĬONFIG:Loading primary settings from config file F:\Torrents\Games\DOS\java\.dosbox\dosbox-0.74.confĪbout to allocate memory 22543kb: 34005kb free When set the cputype to 386 there pile of errors appears in the console.īooting without using -bochs boots fine, booting in 386 cputype with -bochs command throws that. When I use -freesize command jdosbox just quits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |