Path: utzoo!mnetor!uunet!cbmvax!eric From: eric@cbmvax.UUCP (Eric Cotton) Newsgroups: comp.sys.amiga Subject: Re: calling all gurus Message-ID: <3649@cbmvax.UUCP> Date: 18 Apr 88 18:57:32 GMT References: <8804051628.AA27845@decwrl.dec.com| <3482@ece-csc.UUCP| <8190@oberon.USC.EDU| <3484@ece-csc.UUCP| <8214@oberon.USC.EDU> <2161@antique.UUCP> <8725@agate.BERKELEY.EDU> <3635@cbmvax.UUCP> <2178@antique.UUCP> Reply-To: eric@cbmvax.UUCP (Eric Cotton) Organization: Commodore Technology, West Chester, PA Lines: 29 In article <2178@antique.UUCP> cjp@vax135.UUCP (Charles Poirier) writes: >In article <3635@cbmvax.UUCP> eric@cbmvax.UUCP (Eric Cotton) writes: >> V1.3 sizeof(struct Preferences) = V1.2 sizeof(struct Preferences) >>Likewise the length of system-configuration is unchanged. The new >>printer stuff was put in the padding bytes at the end of the existing >>Preferences structure. > >Oops! So my idea of checking the length won't work. So, then what would >happen if someone ran SetPrefs under 1.3 from a 1.2 system-configuration? >Presumably something awful? Though I suppose the reverse might be innocuous, >setting 1.2 prefs from a 1.3 system-configuration? If you have an AMIGA running under V1.3, and used the SetPrefs program (as I understand it) from a 1.2 system-configuration (or simply copied a 1.2 system-configuration file to your V1.3 disk, then booted) there would be no problem. Or vice versa. All the new printer fields default to zeros. Going the other way, V1.2 would simply ignore the new printer stuff if fed a V1.3 sys-config file. -- Eric Cotton Commodore-Amiga *======================================================================* *===== UUCP: {rutgers|ihnp4|allegra}!cbmvax!eric =====* *===== FONE: (215) 431-9100 =====* *===== MAIL: 1200 Wilson Drive / West Chester, PA 19380 =====* *===== PAUL: "I don't find this stuff amusing anymore." =====* *======================================================================*