bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) (05/21/87)
> [This person] comes in > periodically with bootable slideshow disks that he gives them for that > purpose. I've heard this happens at other stores. Apparently it is > technically illegal. [goes on to talk about INSTALL] After reading your message, I took the hacker approach, reached deep into my assembler archives, and cooked up: ----------- Public domain install ---------- begin 777 install M```#\P`````````"``````````$```!B0``!$P```^D```!B+'@`!$/Y````A M(DZN_F@L0$'Y`````")()CP```#_<``A0``$1/P``"(9T8%1R__Z1(!3@"%`D M``1P`&$``*QF"D'Y```$`'8D8`A!^0``!"1V%"0(3J[_Q"(`9PA.KO_0<`!.B M=7`43G4O"B(\``$``7`B3J[_.B1`2H!G%'#_3J[^MG+_LH!F#B)*<").KO\NB M)%]P`$YU%4``#Q5\````#A5\``0`"$(J``F3R4ZN_MHE0``00>H`%""(6)!"! MJ``$(4@`""`*)%].=2\)</\30``((T``%'``$"D`#TZN_K`B7W`B3N[_+DCG3 M(!(L>``$)DB?_````#AP-R!/0AA1R/_\80#_9&<``&@O0``.'WP`!0`(0?D`1 M``0X(D]P`'(`3J[^1$J`9D@_?``#`!PO?```!```)$*O`"PO2P`H(D].KOXX4 M$"\`'V8F/WP`!``<(D].KOXX/WP`"0`<0J\`)")/3J[^.'X`'B\`'V````1^, M_R)O``YA`/]2W_P````X3-](!"`'3G4```/L````!0````$```$6````3```< M`$(````2````!@````````/R```#Z@```1-$3U,``````````W`L>``$0_H`. M$$ZN_Z`@0$J`9A!3@$YU9&]S+FQI8G)A<GD`(&@`%G``3G4`````````````; M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````````````````````````````````````````````` M````````````````````1&ES:R!I;B!D<FEV92!$1C`Z(&ES(&YO=R!B;V]T4 M86)L92X*26YS=&%L;"!$1C`Z(&9A:6QE9`IT<F%C:V1I<VLN9&5V:6-E````D %`````_(*_ `` end ------------------ The parser code relies on some stuff that you do not have, so it was omited. This version of install works for drive DF0: only. This code will only make the disk bootable. Unless a "devs:system- configuration" file is created it will come up with the standard yucky colors and font. Unless a "s:startup-sequence" file does something (like start a slide show), this will be a very boring disk indeed. Without workbench disk files you will not be able to use: RAM: PRT: PAR: SER:, narrator, clipboard, the disk validator, mathtrans.library, icon.library, translator.library, info.library, mathieeedoubbas.library, version.library, diskfont.library or any CLI commands You may be able to snake out of the RAM: restriction with VD0: or VDK: and the public domain "MOUNT" command that someone (Perry?) had. ------------------------------ You do NOT need to require CLI knowledge to execute a script that would copy workbench files from a user's disk to the product disk. A file that was passed 'round a while back called "ICONEXEC" will give a Workbench icon to a CLI command. I do not have a copy, but it probably ended up on a FISH disk. ----- Some technical info ---- The boot record is of this format: dc.b "DOS",0 ;Signifies DOS type disk dc.l 0 ;Checksum goes here dc.l 880 ;Unused and/or root key ... ;Code See the V1.1 ROM Kernal Manual Appendix L for the passed args to the code. The code in the the install above serves just to kick DOS in the pants. Just before that happens is a great time to make all sorts of clean patches and replacements. After DOS is up certain things may get a bit messier to replace. The huge array of zeros is the empty part of the boot record. This is fenced off in it's own area of the DATA hunk for easy non-source modification. The checksum is computed on the fly, so feel free to cusomize the code in any way you see fit. OO \/ send all litigation to: bryce@cogsci.berkeley.EDU
keithd@cadovax.UUCP (Keith Doyle) (05/23/87)
In article <8705210803.AA16321@cogsci.berkeley.edu> bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) writes: > >After reading your message, I took the hacker approach, reached deep into >my assembler archives, and cooked up: > >----------- Public domain install ---------- Thanks guy, this should make life a little easier. >\/ send all litigation to: bryce@cogsci.berkeley.EDU Actually, I was wondering where I might send a copy of one of these 'demo' disks like I was talking about to you for appreciation of your little 'hack'. Keith Doyle # {ucbvax,ihnp4,decvax}!trwrb!cadovax!keithd # cadovax!keithd@ucla-locus.arpa Contel Business Systems 213-323-8170
andy@cbmvax.cbm.UUCP (Andy Finkel) (05/23/87)
In article <8705210803.AA16321@cogsci.berkeley.edu> bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) writes: > >> [This person] comes in >> periodically with bootable slideshow disks that he gives them for that >> purpose. I've heard this happens at other stores. Apparently it is >> technically illegal. [goes on to talk about INSTALL] <well, someone has to do it....> First of all, let me set your mind at rest. There really isn't a problem with distributing disks that have had our 'Install' program run on them. That was a case of people 'assuming'. Its the files on the disk that is the issue here. (so, enough install programs already!) Now that we've had to take official notice of the software distributed on complete Workbench diskswe'll come up with something. (Does anyone know what the other computer companies in this situation do ?) Obviously, there are several problems to be addressed; control, royalties, etc. our basic position is: we want to do as much as we can to encourage Amiga use. So give us a little time to work something out. (probably shareware is going to be the most difficult, as a restriction to non-comercial copying without a Workbench license won't do for that.) (Actually, come to think of it, from what I hear from most shareware authors, a non-comercial restriction probably wil cover them :-) ) Finally, you *can* (as everyone has pointed out) do a bootable disk without any Workbench files at all. You make your own startup sequence. (and you can use system-configuration; I don't see any problem there) As long as your disk is write protected, there's not even an excuse for the validator to activate. So the 'self-starting demo' problem is non existent, anyway. unofficially, andy finkel -- andy finkel {ihnp4|seismo|allegra}!cbmvax!andy Commodore/Amiga "An end is always a new beginning." - Captain Cloud Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.
hah@isum.intel.com (Hans Hansen) (05/23/87)
In article <1919@cbmvax.cbmvax.cbm.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes: >In article <8705210803.AA16321@cogsci.berkeley.edu> bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) writes: >> >>> [This person] comes in >>> periodically with bootable slideshow disks that he gives them for that >>> purpose. I've heard this happens at other stores. Apparently it is >>> technically illegal. [goes on to talk about INSTALL] > ><well, someone has to do it....> > >First of all, let me set your mind at rest. There really isn't a problem >with distributing disks that have had our 'Install' program run on them. >That was a case of people 'assuming'. Its the files on the disk that >is the issue here. (so, enough install programs already!) > >Now that we've had to take official notice of the software distributed >on complete Workbench diskswe'll come up with something. >(Does anyone know what the other computer companies in this situation do ?) > Come on Commodore... Get your head screwed on correctly ! The only reason you should worry about your software being passed around is if there are A1000 CLONES out there that can also use the programs. THERE ARE NO A1000 CLONES... All of the people that would be receiving the WB disks with the PD software on them have already paid for the right to use it. Take a step back and LOOK AT THE HARM that you can cause by continuing to be ROYAL JERKS about this. Hans (ex C-A Test Engineer/ATE developer forthe A1000)
scotty@l5comp.UUCP (05/25/87)
In article <1919@cbmvax.cbmvax.cbm.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes: >First of all, let me set your mind at rest. There really isn't a problem >with distributing disks that have had our 'Install' program run on them. >That was a case of people 'assuming'. Its the files on the disk that >is the issue here. (so, enough install programs already!) > > unofficially, ^^^^^^^^^^^^ > andy finkel So IS this the 'offical' line on install or not? In any case, the PD install programs don't write trash out to the disk. And as I pointed out said trash CAN include SOURCE code or OTHER embarrasing items... If you run a text editor alot I found that the chances of install grabbing ram with some text editor text in it were VERY high. The PD install programs also allow authors to make disks that come up and say "Don't boot me silly! (RTFM)". They could of course setup the startup-sequence to do this, but then when the disk was copied to a workbench disk it'd still have that startup unless they supply TWO startup files... And life is tough enough already. :) Scott Turner -- L5 Computing, the home of Merlin, Arthur, Excalibur and the CRAM. GEnie: JST | UUCP: stride!l5comp!scotty | 12311 Maplewood Ave; Edmonds WA 98020 If Motorola had wanted us to use BPTR's they'd have built in shifts on A regs [ BCPL? Just say *NO*! ] (I don't smoke, send flames to /dev/null)