If you "save as" "web page complete"... its all inclusive in a single file..you have do do each page and mane that folder what the thread was called.

__________________
Proud owner of ....
1971 280SE W108
1979 300SD W116
1983 300D W123
1975 Ironhead Sportster chopper
1987 GMC 3/4 ton 4X4 Diesel
1989 Honda Civic (Heavily modified)
---------------------
Section 609 MVAC Certified
---------------------
"He who fights with monsters might take care lest he thereby become a monster. And if you gaze for long into an abyss, the abyss gazes also into you." - Friedrich Nietzsche

I would be careful what you say there...

...there are intelligent individuals being born everyday immersed in the world of technology that the "seasoned professionals" learned. The past has its place but so does the future.

Have you ever heard of eVault? They essentially backup your data over the internet to a remote site they maintain. If a restore is needed, they perform it from their end as well. No fuss, no muss for you.

__________________
1980 300SD (352K)
1978 Chevy Nova (30K original miles)
1994 Dodge Caravan (146K) 4 cyl - why?
1999 Toyota Corolla (Neo synthetic only please)

I've been making money with microcomputers for 30+ years, and I've learned:

0. When possible, downtime makes backups and restoration of those backups much easier. Does this system, for example, REALLY need to run 24/7? Everyone seems to make 24/7 a requirement these days, even if it is completely unwarranted. If people understood what truly reliable 24/7 operation cost over 23/7, they might think differently.

1. Trust NO backup until you see, _with your own eyes_, a disaster recovery/restoration drill, timed, and the end result tested.

2. Explain to management the relationship between backup techniques, money, and time. Less time to recover = more money, with zero restoration time (i.e., failover) costing the most. Generally, you get what you pay for. Except for when the installation of a $15,000 (1997) DDR robot tape backup system by an $80/hr consultant idiot destroyed an Oracle database containing about 10,000 man hours of data that I was managing and backing up fine all by myself to CD before this happened (file by file backups of a live Oracle database not running in archive mode=very bad idea).

3. For REALLY important backups, use two completely different systems and technologies, and store the results of at least one offsite. Extensive logging,_MONITORING_, and random QA of the backups is CRITICAL.

4. "RAID" is NOT a "magic bullet" that makes systems invulnerable. I've seen RAID controllers fail and spew garbage over every drive. I've also seen bad SCSI drivers corrupt drives, and the data faithfully replicated by the perfectly functioning RAID. I've seen a $20.00 CPU fan fail, the CPU overheated, and then it proceeded to emit chunks onto files stored on the six-figure SAN that it was connected to.

__________________
86 560SL
With homebrew first gear start!
85 380SL
Daily Driver Project

http://juliepalooza.8m.com/sl/mercedes.htm