home *** CD-ROM | disk | FTP | other *** search
- Path: soap.news.pipex.net!pipex!usenet
- From: m.hendry@dial.pipex.com (Mathew Hendry)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Want to boot FAAAST? -problems
- Date: Tue, 5 Mar 96 01:46:59
- Organization: Private node.
- Distribution: world
- Message-ID: <19960305.4D8E60.2485@am183.du.pipex.com>
- References: <199.6630T608T838@login.eunet.no> <347.6631T956T857@stud.cs.uit.no>
- NNTP-Posting-Host: am183.du.pipex.com
- X-Newsreader: TIN [AMIGA 1.3 950726BETA PL0]
-
- Mike (Mike@Redrobe.demon.co.uk) wrote:
- : Whilst fastboot does what it says it does, I'm not currently using it for
- : these reasons:
- :
- : 1) the diskchange command doesnt seem to work when using runback (even other
- : versions of runback..) ..see below
-
- Works fine here.
-
- : 2) when diskchange works ...it basically makes my system useless due to
- : assigns/paths used by workbench...
-
- I've had no problems with this either. What filesystem are you using? Assigns
- and paths should not be affected by DiskChange. Don't you remember running
- your old Amiga off floppies only and having to swap out the Workbench disk the
- whole time? This is equivalent to running DiskChange. Were your assigns and
- paths affected then?
-
- : Am I right in thinking that if diskchange isnt run directly after a "fastboot"
- : boot up, then your HD is in mortal danger the next time you write to it?
-
- Yes. The system has to know that the hard disks may be in a different state
- than they were when the grab was done. File pointers used by programs will
- become invalid if the system is not informed of the disk change, and this
- could give you SERIOUS problems. SERIOUS = Munged hard disk. You don't want
- that to happen, really.
-
- One problem I did encounter was that my disk cache program (HyperCache) became
- unstable if I allowed it to be grabbed. This is probably obvious. Putting it
- in FastBoot-Startup and removing it from my normal Startup-Sequence fixed
- things. Analagous commands such as AddBuffers should probably be moved to
- FastBoot-Startup as well, just to be safe, though I suppose that they respond
- to disk changes properly.
-
- I also added a command to FastBoot-Startup to copy the contents of ENVARC: to
- ENV: - I don't want to have to do a new grab every time an ENV: setting is
- changed. I used "Copy ENVARC:~(Sys) ALL QUIET" so that screen mode prefs etc.
- would not be copied (otherwise IPrefs would bring up a the familiar "close all
- windows except drawers" requester). Any good program which supports file
- notification when settings are changed should work fine with this. If not,
- you'd either have to move the offending program to FastBoot-Startup or grab
- the system every time that program's settings were changed.
-
- Another problem I had was the virus, of course, but then I _always_ check
- archives for viruses before using them, particularly when those programs
- claim to cut boot times down to 3 seconds ;)
-
- -- Mat.
-