ugblaszy@sunybcs (Dave Blaszyk) (05/13/88)
In recently purchasing Manx 3.6 C compiler with SDB for the Amiga, I was hoping to finally do some serious hacking, since I am finally graduating. I began to read the manual on MANX C. I was hoping to run MANX, on a vanilla A2000 ( with (1) floppy, and (1)meg of ram, and using VD0:). In reading the section, on setting up for one floppy drive, they suggest to trim the SYS1: disk to use this as a workspace. This seems stupid, I have at least one meg of Ram, could I not just put the libs and my C source code in VD0:? This would decrease access to the drive and hopefully increase compile and link time. Here is my question, to anyone with a helpful hint on working on a 1 drive system, (and NO I cannot afford anymore HARDWARE!), ?????????????????????????????????????????????????????????????????????? How can I setup my MANX C compiler with my current system, what startup-sequence is best, how can I use SET commands to help in finding the important libs and include's. Could I also put SDB, either on the SYS disk or in VD0, Is Ronald Reagan really ALive? ?????????????????????????????????????????????????????????????????????? Any help in this problem, would be much appreciated, Please only send me mail do NOT repost or follow-up. And if you are wondering why I did not figure this one out myself, I am too lazy to figure out all the details myself, especially if someone else already knows the answer. --DvBlaze
ali@polya.STANFORD.EDU (Ali T. Ozer) (05/14/88)
In article <11212@sunybcs.UUCP> ugblaszy@sunybcs.UUCP (Dave Blaszyk) writes: > I was hoping to run MANX, on a vanilla A2000 ( with (1) floppy, >and (1)meg of ram, and using VD0:). I would mail to you directly if I could, but I can't. I know a person who was developing on a 512K, 1 floppy Amiga until last night (when his 2 Meg expansion finally arrived). You can fit cc, as, ln, emacs, the include files, c.lib (or c32.lib), and various CLI commands such as list, copy, etc, on a single floppy, and still have 8-9% of the disk empty. For doing small development, this might be fine. For speed, copy cc, as, and c.lib into VD0:. For bigger projects, you might copy most everything from the boot disk to VD0: (possibly filling up half your memory), then take out the boot disk and stick in your work disk. One problem with this is that everytime you guru, you'll have to insert the boot disk in. (This will be remedied when we all have 1.3, with recoverable RAMdisk boot. Right?) You might also look into using precompiled header files --- if you're working on a project for which you have a good idea of what system .h files you need, you can create a precompiled header file, put it on your work disk, and thus avoid copying all the .h files into VD0: during boot time. This also speeds up compiles considerably. In my experience, you will not be able to fit SDB on the boot disk with the other Manx stuff. I usually put a copy of SDB on my work disk. Ali Ozer, ali@polya.stanford.edu