/[projet1]/public/pc/tools/osdk/main/Osdk/_final_/documentation/doc_issues.htm
Defence Force logotype

Contents of /public/pc/tools/osdk/main/Osdk/_final_/documentation/doc_issues.htm

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1002 - (show annotations)
Sun Dec 8 10:50:26 2013 UTC (5 years, 11 months ago) by dbug
File MIME type: text/html
File size: 3040 byte(s)
Resynchronized my own changes to the OSDK with what was in the depot.
From now on I will continue the changes directly with the depot version, and try to update more regularly.
The reason I had this big change is that I had two computers with local changes done in demo parties when working on demos, where I did the fixes to handle Euphoric and Oricutron, plus new tools, modified tools, etc... giant mess.
I do not guarantee that what is on the depot is bug free, but it's the version I'm using right now (My OSDK var points to the public\pc\tools\osdk\main\Osdk\_final_ folder.
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
2
3 <HTML lang=fr dir=ltr>
4 <HEAD>
5 <meta name="robots" content="noindex">
6 <meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
7 <title>OSDK - Known issues</title>
8 <link href="documentation.css" rel="stylesheet" type="text/css">
9 </HEAD>
10
11 <BODY>
12
13 <hr>
14 <A href="documentation.htm"><img src="arrow_back.gif"></A>
15 <img src="pics/osdk_logo_small.png">
16 <hr>
17
18 <h1>Known issues</h1>
19
20 <p id=chapter>Code generation problems</p>
21
22 <p>Even if it has been seriously tested, unfortunately some bugs remains in the code generator, so it's possible to have
23 code that will not compile at all, or code that will compile but crash :(
24 </p>
25 <p>In this eventuality, all you can do is to send us the faulty code in order to allows us to correct the OSDK.
26 </p>
27
28
29 <p id=chapter>C Code performance</p>
30
31 <p>Let's face it, the C compiler is crappy. But you should know that it is a lot better than some others !
32 There are professional C compilers for embeded computing, that generate high quality code, but unfortunately
33 they are very, very, very expensive, do you really wish to pay $3600 to develop in C on the Oric ???
34 </p>
35
36
37 <p id=chapter>C++ comments in assembly source code</p>
38
39 <p>It's kind of working, but generaly fail. Just be aware of that, it's one of these things that will be corrected one day.
40 </p>
41
42
43 <p id=chapter>Compatibility with other Oric models</p>
44
45 <p>Code that does not rely on the ROM calls should work correctly on all Oric models. If the code uses the OSDK library,
46 you can bet it will work only on the ATMOS because most functions are calling the ROM to perform simple tasks like outputing
47 a character to screen or reading the keyboard. Since floating point values support is done using Basic routines, the problem is the same.
48 </p>
49
50
51 <p id=chapter>WriteDSK and Windows 2000</p>
52
53 <p>Due to its nature, WriteDsk needs low level access to the floppy disk controler.
54 Unfortunately this is not working under windows 2000. Even using VmWare or VirtualPC
55 will note solve the problem. The only solution is to create a bootable dos floppy,
56 put the DSK file and WriteDsk, and hoping it will work fine.
57 </p>
58
59 <p id=chapter>Windows 7 and Vista</p>
60
61 <p>The OSDK still contains some old dos applications (mostly tap2cd, tap2dsk, ...). Unfortunately Windows7 and Vista have dropped the DOS compatibility layer.
62 Until these applications get rebuild for Windows they will not run except by using something like DosBox. TapTool and DskTool are new replacements that can be used instead.
63 </p>
64
65
66 <p id=chapter>Problems running Euphoric</p>
67
68 <p>It has been reported that if you install the OSDK in a path that contains the word DEV (like D:\emul\oric\dev\osdk) Euphoric
69 will keep complaining about not finding "message.txt" in his directory. Just avoid doing that :)
70 </p>
71
72
73 <hr>
74 <A href="documentation.htm"><img src="arrow_back.gif"></A>
75 <img src="pics/osdk_logo_small.png">
76 <hr>
77
78 </BODY>
79 </HTML>
80
81

  ViewVC Help
Powered by ViewVC 1.1.26