Sorry not to nag... computers are not infallible, although we rely on them every day to perform work for us. they are not like a toaster or a can opener. they do have problems and can fail at any time. ALWAYS backup your data, and frequently, there are a few good programs that can make backups easier, store your files on a memory stick, or use an external hard disk, disk is cheap Backup your files weekly, or monthly and every so often take a copy of your data and put it a your safety deposit box. you will save yourself alot of pain when the inevitable happens. sorry for the rant, i'll step down off my soapbox.

Bookmarks and Scrapbook are different. I can back up Bookmarks easily following the path I gave in my first post. There is a file for Bookmarks inside the next stop after Profiles, which is v20fqq3t.default. I forgot to mention that last one. There is also a folder for Scrapbook inside v20fqq3t.default, but that folder contains a number of files, including "Backup" and several RDF files that appear to be individual backups but are just a meaningless list of figures when I click them, as well as a folder for "Data." "Backup" itself is also full of lines like the following: RDF:Description RDF:about="urn:scrapbook:item20060912103442" NS8:id="20060912103442" NS8:type="" NS8:title="Scappy String Quilt Instructions" NS8:chars="UTF-8" NS8:comment="" NS8:icon="" NS8:source="http://home.pmt.org/~awalter/string.html"/ So I don't see how saving Backup would give me something to use in the event of a crash. Groan. Come to think of it, Roxio appears to insist on individual files rather than folders when I want to burn a disk, so maybe I'll have to export everything to the desktop and then laboriously transfer it to Roxio as a "project" and burn that. What gets me is that previously--maybe a long time ago--there was just one folder that I could transfer to a zip disk and from it open up FF again with all the scrapbook entries. Somewhere along the line that changed. I do find Scrapbook very useful because any Web page saved there is always there, along with its clickable links, even if the original page has been taken down.

Mother nature certainly has it in for Queensland :-( We had a massive squall here last Saturday with 120kmh winds, pretty well wrecked our town along with several other towns nearby. Our electricity was off for three days and some still don't have any. Just ducky with the 40C+ heat we've been having. Our garden is a mess but the trees all landed on replaceable stuff like the fig tree, the rose bushes and the lawns. We lost 25 metres of front brick and wood fencing, smashed down the garden beds but at least the roof stayed on which is more than can be said for many :-( The town looks like a war zone and the sound of chain saws dominates the air. Surprisingly many people in Perth have little knowledge of this event which happened only 100km from their doorsteps (though it was in the news). We called friends to postpone their visit and the reaction was "A storm? Really? We didn't get any of that cyclone" (the squall was driven ahead of a freak cyclone that was well south of their usual range).

Yes! And it's driving me slightly bonkers! It's not crashing. It's taking forever to load sites. I'm no novice when it comes to computers so, as one might suspect, I've been in, around and through this PC with a fine toothed comb trying to identify and eradicate/correct whatever is causing the problem. I've loaded and unloaded FF v. 50.0 and am currently resting in v.49.0...which once appeared to be the stablest of the later versions. Initially...this whole problem seemed to start with v.49.2. Even FF blog posters complained of delayed uploadings...and the arrival of v.50. was supposed to correct the problem. Hasn't done so on my end. Originally...I thought it might be my ISP...but I've cleared them of any involvement. Then MS and Adobe provided some current updates that were supposed to resolve this issue when it involved their programs. I don't know if they helped or hindered...but they didn't fix the problem. All I can suggest at this point is to ride out the storm. Perhaps a few more days will correct the problem. I may give v.50 a try again. Personally...I suspect it's caused by the newest encryption code that FF is using...but I can't prove that. It's just a gut feeling. I, also, think that most future programs are going to be geared towards MS 10 and that may be why those systems aren't experiencing this particular problem. Incidentally...I'm operating MS 7.1 with no current intention of upgrading. If I have any success reversing the problem on my end...I'll post about it.