This repository has been archived by the owner on Oct 12, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathCHANGES
167 lines (126 loc) · 6.96 KB
/
CHANGES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
This file contains somewhat "official" releases, and important steps. For
proper ChangeLog, you should have a look on the GIT (github) commit log:
https://github.com/lgblgblgb/xep128/commits/master
This file only contains the *key* features of *bigger* releases (milestones,
etc). Newer releases at the top ...
*** CANDIDATE *** MANY CHANGES, version number has been also changed from 0.3 to 0.4!
*** UNRELESED *** !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
* FILE: supports write/save too!
The usual char/block write EXOS functions should work.
Writing after end of the file (after seek) should work,
see later.
* FILE: supports EXOS 10 handler (file hander style func)
(Suggested by Zozo, thanks)
File size, file pointer can be read, file pointer can be
set too ("seek"). Protection byte can be written/read
but it's not stored if channel is closed (and it seems EXOS
don't use protection byte too much anyway).
* FILE: correctly handles the open/create channel calls,
on open, RD/WR file mode is used, but if host OS would deny
this, still, read-only mode is tried to be open (it will cause
EXOS error code returned on exos write char/block calls
on that channel, of course)
* FILE: allows to seek, even over end of the file, giving EOF
EXOS error code on trying to read, and extending file size
to the given offset if written. Host OS file size is
cached/calculated to avoid heavy usage of stat() functions
towards the host OS.
* New config option / CLI switch and also monitor command: DDN
It's default device name. Value of none (in case of config/cli)
doesn't set one. Otherwise, the desired value is set. If you
set this FILE (without ":"!) then the default device driver
will be the FILE: fileio stuff. You may try to set DISK
to set back to EXDOS stuffs (or in theory TAPE, but since
Xep128 doesn't support tape, it does not make sense). Note
that you can give invalid values which results normal channel
functions fail with "device does not exist" error.
* New config option / CLI switch filedir
It sets the default directory for FILE: operations. Of course
you still can use :XEP CD command to change this run-time,
or using the file selector window to do that.
* FILE: supports deleting file on "destroy channel" EXOS call
* !! SD card is finally *writable* from EP, not just read only :) !!
* Dave left/right channels were swapped according to Zozo :)
[well, I have mono sound here even for my PC :-P]
* Re-worked EXOS error code handling with XEP ROM / Xep128
own errors. Xep128 currently used error code 1, with custom
msg answered in case of EXOS 28 call
* New Xep128 icon, thanks to gflorez! (also thanks for testing
Xep128 so many times ... and EnterMice details)
* Native GUI file selectors (GTK on Linux, windows API on Win32)
Currently it's used only by FILE: _loading_ if no file name was
given. Navigating to another directory within the chooser before
selecting file will cause to modify the fileio cwd, that is
all further ops (even from just EP with given file name!) will
use that directory.
* Minor keyboad layout fixes:
right shift was not mapped (reported by gflorez)
alt was not mapped (reported by Zozo)
* ROM configuration allows to manually place XEP internal ROM
with giving a rom@xx option with name XEP (without @, or anything)
Also, XEP internal ROM can be disabled with xeprom 0 option
(only if it's not used in rom@xx to manually place it).
Disabling XEP ROM can be useful to test a software when someone
wants to be sure, that XEP ROM does not cause the problem ...
Of course disabling XEP ROM will cause the lost of :XEP
commands and FILE: interface.
* All loaded ROM at every 16K is checked for signature
XEP__ROM (two "_" signs!) at the beginning of each segment.
If signature found, XEP ROM will be installed there,
overwriting that segment! Note, that :XEP RAM layout
display routine will show somewhat odd result but you
don't need to worry, it's just display :) At some point,
we will stop use combined.rom anyway, especially if auto-install
(via HTTP...) will be ready, which can load ROM images for
the user from the web at the first run of Xep128 if they
didn't exist.
* New build system (not so much interesting for end-user ...)
* Using newer gcc/mingw for Windows builds I put on-line as
the "official version" in the hope that it can be faster
* Z80ex has tighter integration into the build process / dependency info
* At least SDL version 2.0.4 is required from now (many condition etc
can be dropped, QueueAudio stuffs can be used in the future)
* More precise timing, using performance counters and nanosleep()
(usleep() on windows though).
* Arch-dependent GUI iterator is called from per frame func as well
(in case if needed in the future), init can fall back with some
sane feedback (ie, GTK init_check instead of plain init)
* Lame .deb package builing from Makefile (without source package)
* Win64 builds (Windows 64 bit) as well
* Travis-build tests for Linux 64 bit, Windows 32 and 64 bit,
and recently for OSX too!
* If _default_ SD card image cannot be found, Xep128 offers to
create an empty image file for you.
* Ability to load ep128emu snapshot files, limited precision
of state restore only though ...
2016/Apr/07 --------------------------------------------------------------
* FILE: functionality, currently buggy and ugly code, only reading!
It's about accessing files directly from host OS FS, much like
FILE: in ep128emu.
Default directory: files inside the preferences directory.
No support for UI based file selection, file name and/or path
must be provided. Example:
LOAD"FILE:mandel.bas"
No support for setting FILE: as the default, so you must use
FILE: all the time.
* XEP/MONITOR commands DIR and CD to show/navigate on the host OS
directory tree (what FILE: would use). Output is really ugly,
and unsorted. Only files are shown with size under 64K.
To show what is the current directory FILE: would use, issue
a CD command with :XEP or monitor/console.
* skiplogo command line switch or configure file option to skip
the Enterprise logo (uses XEP ROM which modifies the CRDISP
EXOS flag).
* Ugly 4 colour text mode support (still Nick rewrite is needed!)
Bricky Prise seems to work.
* Joystick support via game controllers and/or joysticks, what
SDL can support (the numeric keypad can be still used though).
Currently, the first controller found is assigned for axis 0/1
and button 0 whatever they are :-/
Bricky Prise seems to be playable with X-Box 360 game controller
now. Even EPDOS can be :-) However, if your controller/joystick
has axis 0/1 at an insane position or not assigned to the same
handle, it can be odd. TODO: configuration of used axes/buttons
for functions.
* Monitor/Console/XEP disasm/memory dump, I/O port dump commands.
See help command (:XEP help from EP)