![]() Rule1: DO NOT make assumptions about hardwareplatforms. The following are specific programming rules which should be used as guidelines in designing or retrofitting software to run on Japanese machines. All of the problems described can be overcome by using generic DOS function calls, by using enabled Novell standard libraries, and by using some "tricks" described herein. Even simple assumptions like video memory being represented as "character, attribute, character, attribute" prove to be invalid in some cases. In Japan, not only are OEM versions of MS-DOS different from computer to computer, but the BIOS interface for each machine may also be different (different interrupt numbers, different registers used to pass parameters, etc.) In some Japanese computers, timers, addresses used for hardware interrupt controllers, interrupt levels, etc., may be at entirely different locations - or completely nonexistent. Software programs that make hardware assumptions may cause problems. Instead, some hardware manufacturers use their own proprietary hardware, bus interface, video adapter, interrupt usage, memory map, etc. Unlike the U.S., Japan does not have a single, dominant PC architecture. This document has been previously distributed. General language enabling issues are addressed in documents prepared by Novell, IBM, Microsoft, and others. Specific Japanese language programming issues are identified. This document describes special rules for writing software to run on Japanese PC hardware. Specific Japanese language programming issues Technical problems for enabling and localizing software for Japan occur in two areas: This DevNote was prepared by Novell's International Software Engineering group. The best way to enable software is to do it while writing original code. This DevNote offers guidelines in designing or retrofitting software to run on Japanese machines. Companies must therefore either build software that can run on Japanese hardware unaltered or create software that can be easily modified through hardware isolation. In addition, not only are OEM versions of MS-DOS different from computer to computer, but the BIOS interface for each machine may also be different. Instead, some hardware manufacturers use their own proprietary hardware, bus interface, video etc. Trying to boot a PC-DOS 7.Unlike the U.S., Japan does not have a single, dominant PC architecture. LOG: 430184269 ERROR IOCTL:DOS:IOCTL Call 0D:40 Drive 0 unhandled LOG: Mounted FAT volume is FAT12 with 2847 clusters LOG: FAT: BPB says 18 sectors/track 2 heads 512 bytes/sector LOG: Identified 'fdd.img' as C/H/S 80/2/18 512 bytes/sector In the directory where I have a DSKF file and LOADDSKF.EXE, I start DOSBox-X.Įxpecting 2 side(s) - 80 tracks - 18 sectors per trackĪt this point the DOSBox-X LOG contains the following: Trying to convert the DSKF format disk image to standard MFM DSK format in DOSBox-X. But in the interim it would already help if DOSBox-X would recognise it as an unsupported format and throw an error.ġ44US1.DSK: floppy image data (IBM SaveDskF) Ideally that DOSBox-X would recognise the format and handle it. ![]() Trying to boot such a file in DOSBox will cause a stream of "Illegal Unhandled Interrupt Called 6". My understanding is, that it is mostly compatible with standard DSK files, but with an added header. This format is incompatible with DOSBox-X. There are mixed-mode DOS and OS/2 LOADDSKF and SAVEDSKF executables from IBM to handle the format. IBM released disk image files in what is referred to as DSKF format back in the day. This is different then the XDF feature request. Is your feature request related to a problem? Please describe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |