There is a huge amount of hand-written assembly in IS-BASIC, EXOS and EXDOS - there must be loads of bugs!Now found another one in the EXDOS :oops:
I want to help too.....Spanish version also will be updated! :-)
OFF:
New error messages in the 21st centruy:
*** Internet connection error.
*** Server connection error.
The EXDOS has a lot of error codes that have no error messages.Zozo I'd be glad to give that a go although it was so long ago I'm not sure I'd be any better than anyone else!
I think this is because in the original 16K versions the ROM space is very limited so the rare errors don't get messages.
The 1.4 was developed from version 1.3 which uses a 32K ROM, with lots of free space. I want to put messages for all the errors.
I hate so much when a computer displays error code xxx as an error message :twisted:
Bruce, can you help define messages for these errors? Following the original style of the Enterprise error messages.
I will write each specified error code when it has been done.
I assume they are in a compressed format in the ROM.I don't know. Many years ago I used some PRINT STR$(PEEK(x)) in a FOR loop, and I got a lot of messages and basic commands printed on the screen.
I assume they are in a compressed format in the ROM.Yes it is compressed, similar as the EXOS or BASIC ROMs. But only in the original English EXDOS ROMs (16K size). When the German Enterprise company released the 1.3 two languages version (English/German) then the decompression routine and compressed data removed (at source code level), and putted both message tables (English/German) as plain text to the second segment.
Bruce! What do you think about this?:smt023
(Attachment)
What do you think about this?I would leave the colon ( : ) after "by":
I would leave the colon ( : ) after "by":Ok, is it good now? :-)
"Written by Martin Lea & Bruce Tanner."
not: "Written by: Martin Lea & Bruce Tanner."
Ok, is it good now? :-)Yes, it is!
Note: now all commands which existed in 0.3 version but were removed later because of the lack of the ROM space, have been put back in 1.4!
This means: the person who made the modifications had the source code of 0.x EXDOS! Extracted the command routines from the source, for the called routines found the same in 1.3, and then compiled the adjusted routines to free space in 1.3 ROM.You don't think the person who made 1.3 could have done the same as you ie. take the disassembled code from 0.3?
Today when I added the remaining missing commands to 1.4 I used my 1.3 disassembly for adjusting the extracted code from 0.3.
You don't think the person who made 1.3 could have done the same as you ie. take the disassembled code from 0.3?1) the code is similar, but not the same. I think it is from another 0.x version which still has these commands.
Where did the English/Hungarian 1.3 come from?Very good question! :oops:
Bruce! One non technical question :-)Good question! I remember deciding to do the EXDOS CLI this way so you could copy, rename, delete etc easily without having to leave BASIC (an early form of pop up window) but I don't actually remember making it purple, and in fact I was surprised when I saw it purple after nearly 30 years! :oops: :smt021 I don't think it is a colour I would have chosen from free will, I was probably told to make it that colour. I had been looking into easy-on-the-eye colour schemes around that time (IBM had done some research for mainframe terminals) and I don't think purple featured very highly! You could probably change it fairly easily...
Why the purple color selected for paper color in EXDOS CLI? Used a monochrome monitor? :-D
You could probably change it fairly easily...I have already done it :-) What do you think about dark green?
I have already done it :-) What do you think about dark green?Yes yellow on dark green is good. The other combination that works well is white writing on dark blue. But you are doing the work so it is your choice!
(Attachment)
Can you remember why changed the original idea: channel RAM to device RAM? It is too many problems with force closed channels?Once again my memory fails me I'm afraid zozo: I don't recall the change let alone the reasons for it! (It wasn't really my area anyway.) If I had known at the time someone was going to revisit the issues 30 years later I might have taken notes!
If I had known at the time someone was going to revisit the issues 30 years later I might have taken notes!Good idea! If I found a time machine will tell you :ds_icon_cheesygrin:
Zozo you might find that COPY FILE FILE only works for small files - it will read the whole file into memory and then write it out again on top of the original. Fine if the whole file fits into memory but if it doesn't...:oops:Then this happen :-D
I'd say either filename or file name is correct but it sounds as though I was made to change it to file name at some point and missed one! Personally I find filename easier to read.Ok, in 1.4 "filename" will be used at both message.
I'm not sure about error B1h. Does it print any extra parameters for that message (eg. two drive letters)?Only one drive:
I forgot one:I think ”Wrong number of parameters” is more user-friendly, ”invalid” is a bit computer-techy-geeky
9Fh .INP - Invalid number of parameters
In version 1.3 changed to "Wrong number of parameters"
Which are the better?
I think ”Wrong number of parameters” is more user-friendly, ”invalid” is a bit computer-techy-geekyOk, i kept it.
Missing the:For these also are unknow the IS error identifier. Most of them found in the VT-DOS documentation. (.FILEX, ?, .IATTR, .IMAP, .DATA, ? ) But not for the two ones about the RAM disk, because no RAM disk on TVC.
- File exists
- RAM disk already exists
- Invalid file attributes
- Invalid MAPDISK
- Data error
- No RAM disk
Looking the logic of other codes what do you think about .RAMX and .NORAM?Sounds very likely they are the ramdisk error codes! It should be reasonably easy to generate them too to check the error code values!
I do remember we had some re-entrancy issues with EXOS with the Abort/Retry messages - the main program has called EXOS to do eg a file read and it's gone deep into EXOS and the device driver, and then has to print the message with more EXOS calls...Interesting, I will look it is any special routine about this problem.
I don't know if the 0B1h change could have something to do with thisIt is use same EXOS calls as other errors, just the text source changed: moved from error message table to other messages table.
09Bh .OV64kI think this is for protect system area at Page 0. Anyway all old tape released program fixed which are generated this error. Only when found new old program are possible :-)
If EXDOS behaves differently to the other devices isn't this really a bug in EXDOS?
BFh .NOUPB
This is happened when Unit Handler called for sector operations but the Unit Parameter Block not filled with boot sector parameters. Some disk errors also set status bit in UPB for set it is as invalid.
*** UPB not valid
are right?
9Bh .OV64k
Try to transfer data over FFFFh Z80 address. For example read 200h bytes starting at FE00h. It is very frequent error because TAPE, NET and other EXOS devices not checking this problem.
Any good idea for the message?
9Ah .FILE
End of file entry readed from the FAT before it is ending by the file size from directory
My suggestion:
*** Invalid end of file
I think it should be something like "unexpected end of file" or so?Good idea!
*** Memory overflowWhich is the best? Or other suggestions?
*** 64K memory overflow
*** 64K address space overflow
Which is the best? Or other suggestions?I'd go for *** Lazy programmer :evil:
I'd go for *** Lazy programmer :evil::mrgreen:
But if I can't have that I'd go for *** 64k memory overflow :)Ok.
Good idea separating the errors, much less misleading if you get one.
I'd go for either *** Missed data or *** CPU too slow
"UPB is not valid" sounds more correct.It really sounds better but as I can see the error messages from 20 years ago, verbs are very rare in them. That's why I suggest "UPB not valid", without an "is".
It really sounds better but as I can see the error messages from 20 years ago, verbs are very rare in them. That's why I suggest "UPB not valid", without an "is".The main reason for not having verbs in the error messages of 20 years ago is probably lack of ROM space! But I agree - keep the tradition. However a lot of the messages are of the form ”Invalid xxx” so I suggest *** Invalid UPB
Error messages always had the style of a newspaper article title, without verbs. I don't think we should break this "tradition".
Zozo -- where is your modified EXDOS ROM which I will need for the driver to work?There is the current version. Not a final, but working :-)
Szipucsu! Can you check it the new German messages? The HELP screen and errors: 154, 155, 160, 163, 176, 187, 188, 189, 191The help screen seems OK for me.
In the snapshot just press F1 for list error messages. I used the existing messages and Google translate to create new ones, probably not too good results :oops:
It really sounds better but as I can see the error messages from 20 years ago, verbs are very rare in them. That's why I suggest "UPB not valid", without an "is".
Error messages always had the style of a newspaper article title, without verbs. I don't think we should break this "tradition".
I forgot: FCB = File Control BlockThis is important for the German messages, too! That's why I asked about FCB and UPB "What is this".
UPB = Unit Parameter Block
three genders, three endings!Crazy language! :lol:
when do the German messages begin with capital letters? Originaly total mixed... (http://enterprise.iko.hu/errors.htm)I think they should always begin with capital letters. But, in that messages only the nouns are written with capital letters (as nouns in the German language are always written with capital). But I would begin all the messages with capital letters as in English.
174 Unzulässiger ParameterIt is mistyped by Enterprise Computers GmbH :-)
(der Parameter)
You are fast. Only I forgot one accent, and modified the name of "RAM-DISK" to "disco RAM" like in the English sentences.Ok, updated.
Then "No es un disco DOS" is the correct sentence for the reasons I said.Ok, updated. Any more? :ds_icon_cheesygrin:
Do we have room for more explicit messages too?Currently no :-( It also needs to be disassembled.
If you are using an Enterprise 64 with EXOS version 2.0
- You will not be able to use the 'null' filename to load the file
'START' from disk (see appendix E). If you press Fkey 1 [START]
from BASIC, EXDOS will think that you are trying to load a file
from the RAMDISK.
Ok, fixed it, I replaced the ROM file below.