SADOIAN@UOFT02.BITNET (07/14/87)
Has anyone else noticed that GEMBOOT screws up GFA BASIC's edit screen? I first noticed it when running GEMBOOT 1.09, and it still happens now that I am using 1.10. It seems to be related to how many "FOLDERS" are specified in the GEMBOOT.INF file. I have been using 157, which still screws up the GFA edit screen, but not so much as to make it unusable. Chuck Sadoian
rwa@auvax.UUCP (Ross Alexander) (07/15/87)
In article <8707150100.AA13525@ucbvax.Berkeley.EDU>, SADOIAN@UOFT02.BITNET writes: > Has anyone else noticed that GEMBOOT screws up GFA BASIC's edit > screen? [...] re gemboot: the old version ( 1.06 ) gets in the way of MWC 2.0, but the interaction is all in the shell_p_ variable and this is easy to get around. The new version ( gemb1v10.arc ) is however also incompatible and bootfix.prg can't help. Any ideas out there? Further to this theme: hdb2.3 absolutely fouls things up for the MWC ramdisk utility. I have tried every combination and sequence of things I can imagine, and nothing seems to work. Any gurus out there who can help? Because I really do like the MWC idea of a 'frozen' ramdisk ready to install (already containing your choice of files). And I also like the idea of booting from something besides my pokey ol' floppy. But floppy boots it shall be, since C compiles without the ramdisk are only slightly preferable to visits to one's dentist :-) To change the topic slightly: many kudos to the authors of CAP. Nice stuff, gentlemen! ...!ihnp4!alberta!auvax!rwa Ross Alexander @ Athabasca University