GateWay 2.6

Zitat von Pusti64

Oder besitzt gar jemand eine lauffähige Version davon

So wie ich das sehe, sind die dabei .

Im Ordner drivers und gateWay/garteWay sind das die Dateien die im Namen auf 64 bzw. 128 enden. Bei den gwUtils sind es jeweils die Dateien, die a.out heißen. Das sind, so wie ich das sehe, .CVT-Files. einfach durch geoConvert jagen...

Gruß
Werner

Was hat sich denn bei der 2.6er zu der 2.51er geändert?
Und ist die 2.6er einigermaßen fehlerfrei?

Zitat von Pusti64

Und für welchen Assembler wurde der Quellcode geschrieben?
MegaAss ist es ja leider nicht.

Zitat

Jim Collette did all the programming on his Amiga using a 6502 cross-assembler known as DASM. The version of DASM he used was customized to do the type of work he needed to do. You can also download DASM here if you would like to set up the gateWay source code on an Amiga.

Konkreter:

Zitat

Original files as they were last used by Jim Collette
Here's the files needed for setting this up on an Amiga. Look further down for the same source code files in a pkzip format if you want to unpack the files on a different machine and can't handle the .LHA format.

DASM.LHA - Complete DASM assembler with source code.
GWSOURCE.LHA - (453 KBytes) Complete source code for gateWay 2.6

Instructions for the Amiga: You'll need a hard drive on your Amiga because all the files included in the archives take up more than 1mb of disk space and won't fit on an 880K Amiga floppy disk.

Begin by creating a couple of new directories to hold all the files. On my Amiga, the directories are "DH1:Programming/GEOS/" and "DH1:Programming/DASM/". Unpack the DASM.LHA archive to the DASM directory and the GWSOURCE.LHA archive to the GEOS directory.

Next, you'll need to get the custom DASM assembler program copied into your C: directory. There is actually two versions of DASM in the archive. One is the standard version and the other is the custom one that you'll need for assembling gateWay. Look inside the DASM directory and you'll find a directory called c. Inside the c directory is a file called DASM. Copy this version of DASM to the C: directory on your Amiga. It will now be available for use from the command line of a CLI. At this point, that is all you really need from the DASM directory. If you're short on disk space, you can delete the entire DASM directory. Or you can study it if you'd like to see how a 6502 assembler is coded since all of the DASM source code is included.

Next, you'll need to add a line to your user-startup file if you have one in your S: directory. If not, then add a line to the startup-sequence file. Using a text editor, add the following line at or near the end of the file:

assign >NIL geoProg: DH1:Programming/GEOS/gateWay/

This will assign the name geoProg: to the directory where the source code files are located. Be sure to substitute the actual directory you created. The gateWay directory listed at the end of the string above will be created when the .LHA archive is unpacked. So, if on your system, you created a directory called PRG/GEOS in the DH0: partition on your hard drive, your user-startup line would look like the following:

assign >NIL geoProg: DH0:PRG/GEOS/gateWay/

The line in your user-startup file is needed because some of the source code files contain lines of code that make reference to other files and they need to know how to find the files. The files will all be located in the geoProg: directory and other subdirectories contained within. If you move the entire directory to another place, you don't have to edit all the source files, you simply change the one line in your user-startup file.

You're not ready to start assembling yet, because your Amiga still doesn't really know anything about the geoProg: directory. You'll have to reboot so that the user-startup file is re-read and the geoProg: directory name is assigned. Instead of rebooting, you can also enter the same command line in a CLI and it will be effective immediately. You can also do this instead of adding the line to your user-startup file if you don't want the geoProg: directory assigned every time you boot your Amiga.

Now, let's assemble gateWay. On Jim's Amiga, he had a couple of utilities that aren't included here that made things a little easier for him. This would have been a make and a DMake program. With these programs, he could edit his source code files and wouldn't have to remember which ones he altered. By running the make program, a special make file is read and then commands contained within would be executed. The make program would find the files that have been changed and would call DASM to assemble them. Only the changed files would be reassembled. You can do a search on the Internet and possibly find these make and DMake programs.

However, you can still assemble gateWay without them. But, you'll have to assemble each file one at a time and if you make any changes, you'll have to remember which one to reassemble. You'll actually be running DASM in a linker mode. For instance, when you want to assemble gateWay 64, you'll actually assemble the .lnk file that goes with it. DASM will assemble all the source code files that belong to the .lnk file and will provide you with the actual finished copy of gateWay 64 in a GEOS convert format. You can then transfer the file to a Commodore GEOS disk and use Convert 2.5 from within GEOS to convert it into a GEOS format file.

Each part of gateWay is contained in separate directories. You'll assemble the .lnk files in each directory. But before doing so, you'll have to examine the DMakeFile that is contained within the directory to find out what commands you'll need to issue to DASM for the file you're assembling. Let's do gateWay 64 and you'll see how it's done. From a CLI, go to the directory that contains the .lnk file for gateWay 64. It's actually the same directory for both the 64 and 128 versions. There are .if statements within the source files to differentiate between the two versions.

cd geoProg:gateWay

We are now in the correct directory for assembling the main gateWay programs. If you study the contents of the DMakefile in this directory, you'll see it has a line that starts with GW64 and another that starts with GW128. Just below these is the command line for DASM. You'll actually enter the same command from your CLI command line by hand. So, to assemble gateWay 64, enter the following command and hit RETURN:

dasm part.lnk -oGW64 -DREALSMALL

That will call up the DASM assembler and instruct it to perform all the instructions and commands contained within the PART.LNK file. It will create a new file called GW64 and will try to make the code as compact as possible. Remember, the file will be in Convert 2.5 format so it can be transferred to a real Commodore 64 and then converted from within GEOS to GEOS format. For gateWay 128, do the same with the following command line that you'll find within the DMakefile:

dasm part.lnk -oGW128 -DC128 -DREALSMALL

If all of the above instructions worked for you, then do the same for all the other .LNK files you find in the other subdirectories and you'll have created the entire gateWay V2.6 package.

------------------------------------

gateWay source code files in a pkzip archive

GWSOURCE.ZIP - (466 KBytes) Complete source code for gateWay 2.6

Alles anzeigen

Falls dich das nicht abschreckt du nicht anderweitig an die entsprechenden Dateien rankommst, kann ich die auch zur Verfügung stellen.

Zitat von Stuckalf

Was hat sich denn bei der 2.6er zu der 2.51er geändert?

Kann ich Dir nicht genau sagen. Im SourceCode-Paket (siehe hier: GEOS heute ) ist aber eine Liste enthalten.

Zitat von Stuckalf

Und ist die 2.6er einigermaßen fehlerfrei?

Wohl eher nicht. Wenn ich das richtige erinnere, war da z.B. ein massives Problem z.B. mit 1581. Es ist eine unfertige Entwickler-Version von Mitte 1993 ....

Gruß
Werner

PS: Es gab das Archiv damals bei M. Randall. Der Link ist dort noch zu finden, die Seite aber, wo der Donload lag, leider nicht mehr.

Zitat von Pusti64

MegaAss ist es ja leider nicht.

Ja, das Teil kommt aus Amerika.

Der reine Assembler-Code dürfte also "GeoProgrammer"-Format sein.

Gruß
Werner