Re: Backing up a Butler SQL Server
Phil, Butler SQL 2.5.2 (the version I'm using) is Apple-scriptable. The User manual contains a sample script for it (if you don't have access to the manual, let me know, and I'll send it to you). The User manual has a whole chapter dedicated to backup strategies (and the Reference Guide goes into greater detail) and also states the following: Butler SQL includes support for online backups using its Backup command. The Backup command is necessary because it is not possible to make reliable copies of files that are in use. For example, you do not want to backup a database that includes partially completed transactions. Butler SQL's Backup command: * waits until all current transactions are completed, * makes a copy of the one or all of the databases installed on the server, and * detaches the database journal and activity logs. While the backup is in progress no users will be allowed to update the affected databases or begin a database transaction. Users will, however, be allowed to view data in the databases. Once the Backup command has completed normal access to the server will be restored. At this point you can then use your backup software to copy the files to archival media. Refer to the SQL Reference Guide for a detailed description of the Backup command. The backup command can be issued from any application that allows you to send SQL to a Butler server. For example, you could use AppleScript to write an applet that connects to your server, issues the backup command, then disconnects. Here is a simple AppleScript script that will backup a database on a server... ** Good luck, Jim Coefield [EMAIL PROTECTED] Subject: Backing up a Butler SQL Server From: "Phil Geller" [EMAIL PROTECTED] Date: Wed, 13 Dec 2000 07:40:40 -0800 A client is using a Butler SQL Server to support a Panorama database. This database stores data in RAM. I would like to Retrospect server, running on the same system to shut it down, so that the data is flushed to a file, before the backup starts. Butler SQL is not Apple Scriptable (at least without an optional add-on, which may not be available for this version... I haven't researched that yet.) Does anyone have thoughts on the best way to deal with this? What I've done for now is shutdown and restarted the server just before the backup begins. If it works that should update the database file. Phil Geller WorkingMacs Macintosh Consulting for the Small Office and Home Office voice: 650 493-8689 fax: 650 493-8587 -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: Error 212, VXA, Retrospect 4.3
Dave, I'd first follow the advice given me by Ecrix Irena a few weeks ago, and if that doesn't help, most likely your drive is experience some sort of scsi problems with your computer. I'll forward you that post. If that advice doesn't help, I'd contact Ecrix and tell them about your situation. Pulling logfiles and giving them sense information from the drive will help to resolve the situation. Some of us with certain configurations have been working with Ecrix to resolve problems with Retro Mac and VXA drives. They are working on firmware updates to resolve specific problems that folks are experiencing. I have found Ecrix to be most responsive to folks with certain configurations who can help them debug their drives. Jim Coefield [EMAIL PROTECTED] Subject: Error 212, VXA, Retrospect 4.3 From: "David Weeks, weeks.de" [EMAIL PROTECTED] Date: Fri, 03 Nov 2000 00:53:51 +0100 Hello All, two weeks ago we bought a VXA drive which we are running on an Adaptec SCSI card in a PPC 8500/200 with128MB RAM. Backups run just fine and very fast, but after having backed up the entire network (probably 40GB) the next incremental backup suddenly stops and asks for the tape that's already in the drive. This tape is now marked as "gelöscht" which is German for erased or deleted. When this first happened I ejected the tape and put it straight back in the machine and it appeared to recognise it but when I tried to continue the incremental backup it brought up an Error 212 message. When I tried to retrieve data from the tape it appeared to rewind to the correct spot and start to retrieve the document, but then stops and again brings the error 212 message. The first time this happened I thought that I had maybe set up the script incorrectly or had inadvertently deleted the tape. Therefore yesterday I rewrote the backup scripts and backed up the whole network again onto a new tape. This evening I came back into the office to find that todays incremental backup had also stopped and was again demanding the tape already in the drive. All other details are again as described above. This is, as you will surely realise, a very disturbing situation for us as we are now without a safetynet and our old DAT based system simply cannot cope with the amount of data we are generating. if anybody is able to shed some light on this Iwould be very grateful. Best regards, David Weeks -- -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: retro-talk #741 - 10/25/00
Irena, I've had good ideas and response from Ecrix, and we are working on the problem. I think that we'll work it out, one way or another. I have the utmost respect for Retrospect (dozens of my clients use it flawlessly (with many different backup mediums), and I believe that Ecrix is trying its best to bring new technology and products into the tape drive arena to provide good affordable solutions for small to mid-size business LANS. I do think though, that with the VXA promotions, and the newness of the drives, that some of us are doing a bit of beta testing for them (and they have been very responsive in tech support). I hope that we can work all the bugs out, because after looking at many different technologies for backups, initial cost, media cost, techno improvements, etc. I still think that Ecrix has a hot product. It just needs to be tested out in a bunch of different environments, of which I'll admit that mine is a bit unique. And then tweaked for perfection. Thanks, Jim Coefield, [EMAIL PROTECTED] Subject: Re: Retro Mac And VXA Drive From: "Irena Solomon" [EMAIL PROTECTED] Date: Wed, 25 Oct 2000 10:54:38 -0700 Hi Jim, I put these notes in to remind folks that an error 206 with a VXA drive can be caused by factors other than the issue reported on MacIntouch. Ruling out these other factors in your situation pinpoints the problem, thus contacting Ecrix makes sense. I just don't want users to be waiting for information from Ecrix if the problem they are experiencing is not specific to the Ecrix hardware. Thanks, Irena -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: Retro Mac And VXA Drive
Well, I guess Friday afternoon was a bad time to ask this question--didn't get any response, so i guess I'll try again this tuesday morning. Or maybe its just time to RMA the drive... Thanks, Jim Subject: Retro Mac And VXA Drive From: "Jim Coefield" [EMAIL PROTECTED] Date: Fri, 20 Oct 2000 13:50:00 -0600 Could we get an update from Dantz and Ecrix on the VXA/Retro Mac issue, as reported by MacIntouch, 10-20-00 (see below)? The post on MacIntouch goes a long way to explaining some of the problems I've been seeing with my VXA drive. If not for having just finishing rebuilding my LAN and upgrading my net connection, and installing new servers, routers and switches, I was going to dive into troubleshooting the problems I've been having. Maybe all I have to do is wait for the firmware update? I've not only got many 206's, but errors 102 (trouble communicating), 203 (hardware failure), error 205 (lost access to storage medium), error 100 (device rejected command). In addition, after these errors, the drive will not continue to use the current tape, and always wants a new one (whether 4 gigs or 40 gigs were written to it)--leading me to believe the the end of write markers were never properly written, which could leave the tape in an unusable condition. Also, the drive can take up to several hours to eject a tape after one of these errors--following Ecrix's advice to eject a tape: power down the drive, disconnect it from the backup Mac server, turn it on and hit the eject button many times quickly in a row. Makes for a very tedious process of continually regenerating backup sets. I've been using a BW G3/300 with a Miles Initio Blue Note scsi card and OS 9.0.4 with Retro 4.3. Using the VXA tool to maximize capacity over speed seemed to exacerbate the situation. Thanks, Jim Coefield [EMAIL PROTECTED] From MacIntouch: "Just got off the phone with Ecrix tech support. I had just set up my new VXA-1, and was getting a lot of type 206 (bad media) errors from Retrospect. "According to Kelly at Ecrix, this results from what is apparently a timing issue between Mac Retrospect and the Ecrix drive, and is not necessarily a media problem. Kelly says that Dantz and Ecrix have tracked the problem down, and Ecrix expects to release a firmware update to solve the problem within the next week or so." -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Retro Mac And VXA Drive
Could we get an update from Dantz and Ecrix on the VXA/Retro Mac issue, as reported by MacIntouch, 10-20-00 (see below)? The post on MacIntouch goes a long way to explaining some of the problems I've been seeing with my VXA drive. If not for having just finishing rebuilding my LAN and upgrading my net connection, and installing new servers, routers and switches, I was going to dive into troubleshooting the problems I've been having. Maybe all I have to do is wait for the firmware update? I've not only got many 206's, but errors 102 (trouble communicating), 203 (hardware failure), error 205 (lost access to storage medium), error 100 (device rejected command). In addition, after these errors, the drive will not continue to use the current tape, and always wants a new one (whether 4 gigs or 40 gigs were written to it)--leading me to believe the the end of write markers were never properly written, which could leave the tape in an unusable condition. Also, the drive can take up to several hours to eject a tape after one of these errors--following Ecrix's advice to eject a tape: power down the drive, disconnect it from the backup Mac server, turn it on and hit the eject button many times quickly in a row. Makes for a very tedious process of continually regenerating backup sets. I've been using a BW G3/300 with a Miles Initio Blue Note scsi card and OS 9.0.4 with Retro 4.3. Using the VXA tool to maximize capacity over speed seemed to exacerbate the situation. Thanks, Jim Coefield [EMAIL PROTECTED] From MacIntouch: "Just got off the phone with Ecrix tech support. I had just set up my new VXA-1, and was getting a lot of type 206 (bad media) errors from Retrospect. "According to Kelly at Ecrix, this results from what is apparently a timing issue between Mac Retrospect and the Ecrix drive, and is not necessarily a media problem. Kelly says that Dantz and Ecrix have tracked the problem down, and Ecrix expects to release a firmware update to solve the problem within the next week or so." -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: computer synchronizing
Phillip, I'm using Retro 4.3 on the BW G3 backup server running OS 9.0.4, which also is the destination for the duplication (to an HFS+ disk partition). The source is coming off of a PC running NT 4 Service Pack 3 on an NTFS formatted drive. It's always the same files that get reduplicated (or so it seems as they go streaming by in the duplicate window--no file by file logs on duplicates). I can find no rhyme nor reason why it's the same files. They all have the same directory permissions as the root directory that gets sourced by Retro. Subject: Re: computer synchronizing From: "Philip Chonacky" [EMAIL PROTECTED] Date: Fri, 6 Oct 2000 09:03:32 -0400 Which platform are you running for Retrospect? I have found that there are enough differences between file info on Windows and MacOS, that Retrospect would not match the same file located on the two different file systems. This could be especially true if one volume is NTFS, since Retr.o for Mac doesn't recognize the NT security settings. As a side not, I found this also to be true with Apple's folder synchronization tool with one folder being on a PC formatted disk and the other a Mac drive. Any one else care to comment? -PC -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
[OT] Re: clones and PowerPC computes
rant OK, It's not often that I get into these sorts of me too's, or platform put-downs, but as the proud owner of a Power Computing PowerBase Minitower, and 4 7200's (and many other machines), and having provided support for many Power Computing computers over the years, I've got to say something here. The PowerBase, while based on the 7200 motherboard, made many significant improvements on the original design, including the ability to upgrade the machine easily with the addition of a daughter card processor, not to mention initial processor speeds of up to a 240Mhz 603. PowerBases are easily and cheaply upgraded to G4's, and run rock solid--try that with a 7200 (without an expensive mother board swap). The PowerBase also came with on board IDE, in addition scsi, making the addition of large/cheap IDE drives easy. Not to mention having an extra full size bay for, say, a CD-R; try that with a 7200--no can do. Pop in a good fast scsi drive for the system/apps, and then pop in a cheap IDE for storage, and you've one heck of a fine computer. Yes, the fans were noisy, but a pair of Silencers at $12/each easily took care of that, and you also could easily add a processor fan for $10 to cool that 240Mhz 603 or G3 or G4 upgrade. The Mac 8500 is just as noisy, but thrice as hard to get into and work on. Oh, and lets not forget the built-in vga monitor port to hook up other than Apple monitors without an adaptor. All-in-all one heck of a fine machine for those who like to tinker! I'll be using mine in my home office for years to teach my kids about computers--using and repairing/upgrading them. Ever see an 8 year-old girl put a CD-Rom drive in a computer by herself? Not in a 7200 you won't, but in a PowerBase MiniTower she can. And for the 7200's, I currently run three of them for servers--email, listserve, and web. Yes, they're getting old, and yes I'm getting ready to swap them out, but they've been faultless workhorses--running for 4-5 year's straight without a squeak. I'd rather invest my $$ in bandwidth first, then upgrade the machines. There's many good reasons Apple bought Power Computing. They had great engineers, who were beating Apple to the market with products that had more punch and value than their Apple counterparts, and eating up market share. They had a team of marketing individuals who put together one of the first kick-$^% online stores and excellent marketing campaigns. The $100+ million Apple spent to buy them out was, in addition to eliminating competition that was threatening their success, to bring that expertise in house to Apple--those engineers and marketeers that wanted to work with Apple, that is. Having said all that, I wouldn't hesitate to bring my upgraded PowerBase into my hosting LAN and use it for a backup server, a web server, or use it for any purpose whatsoever. In fact there are hundreds, if not thousands of them out there being used for just those purposes. One only has to go to http://www.powerwatch.com and login to their PowerPC users forum to see the vibrancy and life that still exists in the PowerPC platform. /rant Jim Coefield [EMAIL PROTECTED] Subject: clones From: "Nicholas Froome" [EMAIL PROTECTED] Date: Thu, 28 Sep 2000 12:12:54 +0100 I'm running it on a beige G3 300MHz desktop. I wouldn't trust a Power Computing system as a backup server...those are the Packard-Bell of the Mac clone world. Actually, most of the motherboards are the same as the Apple equivalents. They changed other things like floppy drives and CD-ROM drives to a cheaper 3rd party though. I had a customer that had a Power Computing PPC. Equivalent to the 8500. I opened it up and the motherboard had an Apple part number on it. The processor board was made by someone else. The floppy drive had died within months of getting the system. The CD-ROM drive makes an awful noise, but it still works. The power supply is basically an ATX power supply that was modified a little. I think that is exactly what the first contributor meant when he said he wouldn't trust one! -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: 16 MB catalog limit in 4.3
If this info about a 16MB catalog is true, then why are my catalogs 34MB for a 2 tape VXA set archive (that I will be letting grow indefinitely), and 25MB for a new single tape VXA set (using compression) on a hfs+ formatted drive? Or is this specific to a backup to a single file, and not to a tape? Are catalogs for tape backups handled differently, or is there some built in limit on them also? Jim Coefield [EMAIL PROTECTED] Subject: Re: 16 MB catalog limit in 4.3 From: "Eric Ullman" [EMAIL PROTECTED] Date: Tue, 05 Sep 2000 10:07:25 -0700 Stewart is correct. A file backup set's catalog is stored in the file's resource fork, which cannot grow past 16 MB in size. This issue is covered in the 4.3 Read Me and Retrospect Help. Solving this problem requires *significant* changes to Retrospect's backup set architecture--it's not a simple matter. We are working to address this issue with a future release. In the meantime, the Retrospect Help file suggests the following workarounds: o Perform a recycle backup to the file backup set, which clears the catalog and starts anew. (Backed-up data in the set is removed.) o Perform a new media backup to the file backup set, which creates a new, empty file with an empty catalog. (The old file is left intact with its backed-up data.) o Do not try to copy so many files or volumes to the file backup set. Consider creating separate backup sets for different volumes. o Stop using file backup sets and instead use CDs, disks, or tapes. You may transfer backed-up data in file backup sets to other kinds of backup sets. o Leave the catalog compression option on (it is on by default) to help keep down the size of catalogs. I hope this helps. Eric Ullman Dantz Development -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
Re: Protecting a backup server from prying eyes
Thanks Larry, This sounds like a decent compromise between the extremes (no Protection, the Multiple User work arounds, and high security like DiskGuard or others). I don't think that most folks wandering around my office would be able to figure out that they would need a reboot to defeat Blackwatch. And if they were smart enough to do that, they probably are smart enough to defeat any security system--just open the box, take the drive, and any of a myriad of tools can pull your data off of it (for those times when an intruder may not be an office mate--remember Los Alamos?). This screensaver also sounds excellent for those Macs/monitors that don't support Energy Saver mode. I've given up on After Dark and the other screensavers out there as being too conflicting with the OS or other software. Nice to see that some Apple software engineers can write some usable free apps on the side ;-) Jim Subject: RE: Retrospect and OS 9 From: "Larry Acosta Wong" [EMAIL PROTECTED] Date: Thu, 24 Aug 2000 12:19:38 -0700 Jim, To prevent intruders from disturbing the backup server while it's logged in, use the BlackWatch screen saver http://penumbra.apple.com/blackwatch.html to password protect your computer. BTW, there's a posting on the BlackWatch web site that says: (8/23/00) A patch for Retrospect (versions 4.0 through 4.3) is now available. This patch enables Retrospect to launch in the background when performing a scheduled backup, making it fully compatible with BlackWatch. -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
Re: Duplicating volumes
Garrett, I had the same dilemma, and came up with some reasonable solutions (if you have adequate drive space elsewhere on your network). Beauty of this, is you have two duplicates. I'm assuming that the servers you are referring to aren't your Retrospect server machine--that you are using Retro on one machine to do the backups on separate server machines. Goes like this: Solution 1) Set up two duplicate scripts. The first one will mirror your main server drive to a second machine (a subvolume on that second machine's hard drive works fine). Set this script to go off first. Then create a second script to duplicate the subvolume on the second machine to duplicate back to the second drive on the server. Make sure the time for the second script is set to go off after the first script. Solution 2) If you have two servers with two drives in each, you also could duplicate one server's main drive to the second drive on the second server, and vice versa for the second machine. Solution 3) Alternatively, you can put the second drives on another machine, and just run a duplicate script from your server to it's new location. Then when/if you need the drive, if your main server drive fails or crashes (or you have some other hardware failure), you can just re-hook it up to your main server and away you go, or use the second machine as a backup server while you rebuild your main server's drive, or replace it if it's failed. This also has the advantage of only hitting your main server once for a duplicate. Be forwarned that file sharing privileges will not be maintained during duplicates, as the permissions are always relative to the root of a certain drive (in this case your main drive)--I don't believe that even naming the drives the same thing will maintain those privileges. I have replaced drives on computers, and named them the same thing as they originally were, and then restored the drive via Retrospect, and when I run a regular backup script to tape, I always have to go back and forget the old drive, and add the new one to the script. I believe that Retrospect looks deeper into the drives identity than just it's name and the computer it is on to recognize it on a network (is this right Dantz?). So if you are using Apple's Users Groups with file sharing for, say NetPresenz ftp to use with a web server, then you're out of luck, and will have to reset those permissions manually. Found out this the hard way. Now, if someone else has found a good way to maintain those file sharing privileges during duplicates, I'd love to know! :-). And yes I know that running AppleTalk and file sharing on a server is not a good thing (if you have OS 9 you can use TCP/IP file sharing and turn AppleTalk off), but until I either upgrade to another ftp server that doesn't use file sharing, or upgrade WebStar to v4.x which has a decent ftp server built in, I'm stuck with NetPresenz to allow access to my servers. And I like NetPresenz--wish that Stairways Software would have continued developing it! Jim Coefield [EMAIL PROTECTED] Subject: Duplicating volumes From: "Garret J. Cleversley" [EMAIL PROTECTED] Date: Wed, 07 Jun 2000 10:36:30 -0400 I tried to use the duplicate volume command but it won't duplicate a volume on the same machine?? I have two drives in my servers and planned on just using the duplicate command but retrospect won't allow it. Is there another way or am I looking to another program? G -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
RE: Client installers
I'd be happy to just have new installers, that didn't require you to install one version (like 1.1 for Windows) and then update it (to v5), and allowed you to install the latest version in one step. I've used up all of my PC client numbers, but have quite a few Mac #'s left (that can be used with Windows v5 client). When you go to install the 1.1 Windows client, it won't accept the Mac numbers like v5 does, so you have to go through the stupid step of either deactivating another PC (and , or converting it to a Mac serial #, to "borrow" the number to activate the 1.1 client just so you can update it to v5. It's a big PITA. Maybe there's an easier way to do this, but I haven't found it yet. Jim Coefield [EMAIL PROTECTED] -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
Re: using large hard disk as backup destination
This is what we do in our GIS lab. We automatically duplicate (nightly when no ones working and files are closed) many drives that contain our critical ArcView and ArcInfo data scattered across our network (combination Windows 95, 98, NT4) to a single map server (NT4) via Retro on a Mac (100base-T ethernet) that has several 27 GB hard drives. You just need to make sure that the subvolumes you create on the destination drives, representing the drives scattered across the network, contain enough free space. The map server w/backup drives then gets backed up periodically to tape. This situation seems to keep our map techs happy, as they worry about data integrity once the GIS info has been written to tape, given Arc's unique handling of data structures, pointers, and workspaces. Restores for Arc GIS data have to be done very carefully, and being able to move data from a duplicated drive back to its original location is much preferred to restoring from tape. Took one Arc workstation meltdown, wrestling with the Arc data structure to devise this (hopefully) foolproof system. One gotcha on many PC machines: the BIOS can't handle drives larger than, I believe 32GB without being upgraded. Not all PCs will allow you to upgrade their BIOS, or it isn't worth the time and effort to do so. Found out the hard way, which is why my BW G3 has a nice 34GB Maxtor (which had a disclaimer "inside" the box about this possible limitation), and the PC has 27GB drives. Not often you can one-up the PC/NT support person, when you're the Mac guy in the lab. But in this situation with Retrospect, you sure can. Jim Coefield [EMAIL PROTECTED] Subject: Re: using large hard disk as backup desitination From: "Erik Ableson" [EMAIL PROTECTED] Date: Mon, 20 Dec 1999 17:42:55 -0500 Hmmm - here's an alternate possibility: 1. Set up a folder for each client volume to be backed up 2. Set each folder as a volume using the subvolume option in Retrospect 3. Create a duplicate script for each of these. Using the duplicate function with replace entire HD, you will get a mirror of each volume on the server - retrospect is smart enough to do an incremental duplicate so these should run pretty quickly 4. Then backup the server locally to a handy tape device. This will require more active management and tracking as you won't be able to use Retrospect's advanced search features by client name since it will all be one data source, but if you organize your server structure carefully, you should be OK. You also won't be able to use the smarts of the backup server scripts and will be stuck with scheduled ones (not critical for a smaller backup group tho'). Cheers, Erik Ableson NB - this only works if you have a clear controlled client group that you know exactly the available capacity and can ensure that you have sufficient space on the server. Ancillary issues are that if you have a mix of Windows and Mac clients there are some naming issues that may arise since the Mac can't handle names over 32 characters, and if you decide to try this from a Windows box, you'll need to ensure that you have things set up to properly handle MacOS resource forks. Sigh - nothing's ever as simple as it first looks. -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
