Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: freqmax on June 13, 2014, 03:31:53 PM

Title: Disk space on WB1.3 disk1/1 ..?
Post by: freqmax on June 13, 2014, 03:31:53 PM
Anyone recall how much diskspace there was on Workbench v1.3 disk one there was?

And how many disk kB did it take to get a 80 column shell + WB calculator running from floppy?
Title: Re: Disk space on WB1.3 disk1/1 ..?
Post by: Thomas on June 13, 2014, 04:01:25 PM
For the 80 column shell you need the file system-configuration which is 232 bytes.

To run Calculator you need mathieeedoubbas.library (4688 bytes), mathieeedoubtrans.library (15728 bytes) and Calculator itself (7996 bytes).

Given that OFS divides the floppy into blocks of 488 bytes each, system-configuration needs one block, mathieeedoubbas.library 10 blocks, mathieeedoubtrans.library 33 blocks and Calculator 17 blocks. Plus a directory block for each entry sums up to 65 blocks or 31720 bytes occupied on the disk.

Code: [Select]

Directory "df0:" on Friday 13-Jun-14
Calculator                  7996 ----rwed Today     17:04:26
mathieeedoubbas.library     4688 ----rw-d Today     17:04:16
mathieeedoubtrans.library  15728 ----rw-d Today     17:04:16
system-configuration         232 ----rwed Today     17:04:39
4 files - 65 blocks used

Mounted disks:
Unit      Size    Used    Free Full Errs   Status   Name
DF0:      880K      67    1691   3%   0  Read/Write calc
Title: Re: Disk space on WB1.3 disk1/1 ..?
Post by: vince_6 on June 13, 2014, 06:17:45 PM
Quote from: Thomas;766451
For the 80 column shell you need the file system-configuration which is 232 bytes.

To run Calculator you need mathieeedoubbas.library (4688 bytes), mathieeedoubtrans.library (15728 bytes) and Calculator itself (7996 bytes).

Given that OFS divides the floppy into blocks of 488 bytes each, system-configuration needs one block, mathieeedoubbas.library 10 blocks, mathieeedoubtrans.library 33 blocks and Calculator 17 blocks. Plus a directory block for each entry sums up to 65 blocks or 31720 bytes occupied on the disk.

Code: [Select]

Directory "df0:" on Friday 13-Jun-14
Calculator                  7996 ----rwed Today     17:04:26
mathieeedoubbas.library     4688 ----rw-d Today     17:04:16
mathieeedoubtrans.library  15728 ----rw-d Today     17:04:16
system-configuration         232 ----rwed Today     17:04:39
4 files - 65 blocks used

Mounted disks:
Unit      Size    Used    Free Full Errs   Status   Name
DF0:      880K      67    1691   3%   0  Read/Write calc


:-O
Title: Re: Disk space on WB1.3 disk1/1 ..?
Post by: Oldsmobile_Mike on June 13, 2014, 06:30:03 PM
For reference, calc.exe in Windows 7 is 897KB.  It wouldn't even fit on a floppy disk.  How times have changed!  ;)
Title: Re: Disk space on WB1.3 disk1/1 ..?
Post by: Calimeiro on June 13, 2014, 07:08:54 PM
Quote from: Oldsmobile_Mike;766461
For reference, calc.exe in Windows 7 is 897KB.  It wouldn't even fit on a floppy disk.  How times have changed!  ;)
Not to mention OS W7 itself doesn't fit on a single floppy disc.:rofl: (Stupid comparison, i know).
 Use runtime packer and calc.exe fits (390 kb crunched exe).


BTT: If you got WB1.3 you could check out yourself easily.
If you don't own it, it's waste of time to answer.

You've been asking about x86 ISA advantages, 68k code relocation, asking ppl to compile you "helloworld.c" (DIY!!) and now this thread. you really must feeling bored.
Title: Re: Disk space on WB1.3 disk1/1 ..?
Post by: freqmax on June 14, 2014, 12:11:50 AM
Nah, I tried to figure out how much code that really is need to make a really basic Amiga system run. But was uncertain how much that were needed from the system disk. Seems the answer is more or less 300 kB in total to run OS + GUI and some basic program. The above utilities seems not to be much else than calls to the system ROM. This is of course than way less than the 1024 kB flash that many single chip microcontrollers have nowadays.

And it's little hard to access "a real" computer right now. Otherwise I would have installed and fired up the appropriate software to figure it out.

(I find the complete-system-in-256MB feat amazing even today)