Search found 633 matches
- Fri Feb 14, 2020 8:50 am
- Forum: Software & Programming
- Topic: Handling of 8-colors mode
- Replies: 7
- Views: 2726
Re: Handling of 8-colors mode
Hi, What is the quality of `MOVEP' instruction here, I never used, just reading about in MC68008 reference book. It is `move peripheral' aiding communication with 8-bit peripherals, since QL is 8-bit data bus, I miss the point. Also, what use is ROXL, (`rotate with extend'), why we need extend flag ...
- Tue Feb 11, 2020 7:55 pm
- Forum: Software & Programming
- Topic: zipinfo - qdos header
- Replies: 6
- Views: 2312
Re: zipinfo - qdos header
Not sure if useful, I can now process zips created on `QDOS' showing 64-byte headers when set for file type 1. Example: `gstqlassembler.zip' package, containing GST Assembler, with two executables ASM, and ED. pi@raspberrypi:/usr/src/unz50p1 $ ./zipinfo -H gstqlassembler asm 00 00 47 9a 00 01 00 00 ...
- Tue Feb 11, 2020 6:53 pm
- Forum: Software & Programming
- Topic: zipinfo - qdos header
- Replies: 6
- Views: 2312
Re: zipinfo - qdos header
Ah, thanks, now I see as well.
Code: Select all
zip.h:#define LONGID "QDOS02"
zipup.c: strcpy(local_qe->longid, LONGID);
- Tue Feb 11, 2020 6:41 pm
- Forum: Software & Programming
- Topic: zipinfo - qdos header
- Replies: 6
- Views: 2312
Re: zipinfo - qdos header
Ah, does 02 stands for QDOS version number?QDOS02
$0065, could it mean 02A, `A' as revision?
Tom
- Tue Feb 11, 2020 4:08 pm
- Forum: Software & Programming
- Topic: zipinfo - qdos header
- Replies: 6
- Views: 2312
zipinfo - qdos header
Hi, I am toying with an old source to `unzip/infozip' ver. 5.0p1, me modified to display extra fields. I am dumping info on an executable in `foo_zip' created under `QDOS'. I am getting this $ ./zipinfo -v ~/mdv1/foo_zip myexec_exe ..... 32-bit CRC value (hex): d6420d7b compressed size: 17357 bytes ...
- Wed Feb 05, 2020 9:29 pm
- Forum: Software & Programming
- Topic: qdos-gcc @ arm
- Replies: 11
- Views: 3901
Re: qdos-gcc @ arm
Hi,
Seems almost there.
Testing further...
Tom
Seems almost there.
Code: Select all
pi@raspberrypi:~/ql/qdos $ qdos-gcc hello.c -o hello
hello: dataspace 882 (372)
pi@raspberrypi:~/ql/qdos $ cmp hello x86/hello
pi@raspberrypi:~/ql/qdos $ cp hello ~/mdv2
Tom
- Tue Feb 04, 2020 2:44 pm
- Forum: Software & Programming
- Topic: qdos-gcc @ arm
- Replies: 11
- Views: 3901
Re: qdos-gcc @ arm
Hi, With only little understanding, I put on both machines x86/arm, `libc.a', `glibcc.a' created on arm. There was some debug hint left in `calc_xref()' function, that I uncommented. Linker phase, with creating MAP, and outputting xref, on arm, and on x86, respectively. pi@raspberrypi:~/ql/qdos $ /u...
- Tue Feb 04, 2020 8:02 am
- Forum: Software & Programming
- Topic: qdos-gcc @ arm
- Replies: 11
- Views: 3901
Re: qdos-gcc @ arm
Hi, I am now getting this. pi@raspberrypi:~/ql/qdos $ qdos-gcc hello.c -o hello hello: dataspace 882 (372) But the binary `hello' does not seem right. Some analysis>>> `hello.o' object identical on x86 and arm `hello' executable 16276 bytes, same size on x86 and arm, but has 216 differences `libgcc....
- Sat Feb 01, 2020 8:48 am
- Forum: Software & Programming
- Topic: qdos-gcc @ arm
- Replies: 11
- Views: 3901
Re: qdos-gcc @ arm
In the `main.c' debug code just after `aspass1()' added int main(int argc, char *argv[]) { ... aspass1(); SYM *p; char name[12] = {'\0'}; p = lookup( "_printf" ); //p = lookup( "___main" ); cpyname( name, p); fprintf( stderr, "%x %x %x %s\n", p, p->flags, p->access, nam...
- Thu Jan 30, 2020 7:48 pm
- Forum: Software & Programming
- Topic: qdos-gcc @ arm
- Replies: 11
- Views: 3901
Re: qdos-gcc @ arm
Hi, Started debugging, added `perror()' to `lookup(name)' in `sym.c' presumably dealing with symbols. EDIT changed perror() to fprintf( stderr, ... ) Output to stderr $ as hello.s LC0 LC1 _main ___main _printf L8 So `_printf' is seen, but not dealt with properly, somewhere, somehow. Not sure if this...