Reported gateWay v2.5 Problems as of 5/10/93
 
General
1) RAMBAM problem where bytes in the RAMBAM get moved around during a drive 
swap. Jim supposed has fixed this already, but we've never received the new 
version.
 
2) Something is screwy with the filePad code as well. Reports of files which 
cannot be scratched or moved when they are far down in the file list.
 
MakeBoot
1) Lots of booting problems reported, and they seem to be partially linked to 
MakeBoot and whatever it does to patch the Kernal. Booting from device 10 is 
no longer reliable, yet by using the old MakeBoot from the previous gateWay 
release fixes this (but who knows what else it may break?).
 
Launch
1) Launch currently allocates RAM for switcher. It would be better for 
switcher to allocate this RAM for itself. The problem that really occurs here 
is that if you set up a system with an REU, RAM is allocated for switcher that 
could be used for the RAM disk. Another thing to think about is that perhaps 
we should make switcher an autoexec instead of a gateWay document.
 
2) Launch is an autoexec, and as such can create problems for users trying to 
make the same partition boot both the 64 and 128 versions of gateWay. If 
Launch were to contain code to check which computer mode was currently in use, 
and operate only if the correct mode is asserted, that would solve this 
problem. So Launch for the 64 would then only operate on a 64 or in 64 mode on 
a 128, and Launch_128 would only operate in a 128 in 128 mode.
 
3) Another ideal thing for Launch to do would be to check for the gateWay 
string in memory, and if not present, load in the Kernal (or some similar 
scheme). Perhaps this would finally make it possible to get gateWay running 
from the GEOS deskTop, as the manual states.
 
Switcher
1) Still lots of reports of switcher not working, locking up, etc. Even worse, 
users with RAMLink using native mode partition have reported corruption of the 
RAMLink to the point of losing everything in it during a switch. Will we ever 
get this right?
 
Disk Drivers
1) Extreme weirdness during booting. It appears that the initialization code 
for the drives does something to cause them to error. This has been reported 
happening on a number of different devices. The ones that come to mind are 
RAMLink and the 1571. Some people have also reported a lock-up during boot if 
booting from a device other than a 1541, but with a 1541 on the system. It 
appears that the initialization of the 1541 causes this lock-up of the serial 
bus or something. I've also seen this reported for a 1571, though I have to 
wonder if it was somehow stuck in 1541 mode.
 
2) The Native Mode drivers in particular seem to still be botched. Lockups 
occur after copying a number of files, and even when updating documents from 
within applications. Also, there have been a number of reports of incorrect 
fuel gauges...showing a full disk even on a newly formatted partition. This 
has been reported on FD-4000 and on HD partitions.
 
3) We need to check out the drivers for exchangability, too. I think that even 
I have had problems getting certain drives to come online in place of others. 
This might have something to do with those driver initialization code problems 
that I mentioned.
 
4) Speaking of bringing drivers in later, better check, but I thought that the 
1571 driver's configuration box required you to click on a FORMAT button in 
order to bring it into the system.
 
gWMover
Reported that this allows duplicate gateWay documents to be patched in, and 
also that the gateWay can become corrupted when documents are deleted from it.
 
CMD-Move
Users are still crying for the ability to copy between subdirectories.
 
RBoot
We need to know if RBoot does or does not work, and if not, why. If so, under 
what condition is which RBoot to be used.
 
Quitting to deskTop/gateWay - check drives A thru C (if possible)
