Re: Basic Configuration (Was: Re: Retro)

2001-03-08 Thread Ben Mihailescu

Hi,

I got to say: in a university environment the image/fixed data path
works like a charm. The students (clients) will pretty much mess up a
workstation within 3 months. By having a 4BG Ghost image for NT4 and 2k
download in under 10 minutes and then restore networking and data if any
is the most efficient way to operate for us. Have you ever tried to do a
restore from a backup set with 8 DLT members? It's a lot of trips to the
tape drive...

As far as having IT recommend the way to work in a company/university, I
think is the sanest option: Usually you have 1-10 IT guys and 5-600
users. Can you imagine the scenario combinations? Long live server data
storage!

Cheers, Ben

Pam Lefkowitz wrote:
 
 On 3/8/2001 1:07 PM, "Julia Frizzell" wrote:
 
  Every one of our users is told when they start, and they get frequent
  reminders, that nothing not in the Documents folder (save their
  bookmarks) gets backed up. We keep the Documents folder on the
  desktop so they can get to it easily, and remind them to make aliases
  instead of putting files/folders on the desktop.
 
 Julia,
 
 Seems to me that this is all a matter of how the IT is structured and who
 has ownership and control over data. If the goal is for IT to design and
 determine how users can and should work, then your setup works fine
 (assuming, of course, that everyone saves everything to the designated
 spot).
 
 If, on the other hand, users work in a way that gives them freedom to be
 comfortable in their work environment (therefore, more productive) then your
 method isn't as effective. I had a client who was determined to have IT own
 the workflow and have all documents, etc. reside on the servers. I
 questioned this logic but I never really got an answer as to how they were
 going to handle it when the their boss lost data because he just couldn't
 figure out how to navigate the servers to save his stuff or because he just
 got back from a 3 week business trip and hadn't had time to move his things
 to the server yet. Frankly, if a missed deadline caused by lost data costs
 the company a $x-million fine then something is wrong in the IT
 structure/workflow/strategy.
 
 Obviously, you can see where my preference for user support lies...strongly.
 I believe that IT is there to *support* our users, not to tell them how to
 best do their job. Therefore, I vote HUGELY in favor of backing up desktops
 as well as servers. One can never be too protected.
 
 Whew, quite a rant that was. Think I'll go out for a walk.
 
 Pam
 
 ---
 
 Pam Lefkowitz, President  Core Computing Technologies, Inc.
 voice:847/675-3513fax: 847/675-3564
 Member, Apple Solution Experts/Apple Product Professional
 Dantz Development Solutions Provider
 
 --
 --
 To subscribe:[EMAIL PROTECTED]
 To unsubscribe:  [EMAIL PROTECTED]
 Archives:http://list.working-dogs.com/lists/retro-talk/
 Search:  http://www.mail-archive.com/retro-talk%40latchkey.com/
 
 For urgent issues, please contact Dantz technical support directly at
 [EMAIL PROTECTED] or 925.253.3050.


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:http://list.working-dogs.com/lists/retro-talk/
Search:  http://www.mail-archive.com/retro-talk%40latchkey.com/

For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.



Re: Retrospect client under VMWARE??

2001-01-11 Thread Ben Mihailescu

I'm not sure if it makes a diff, but did you install vmware on a raw disk
or as one big file?

Ben

Toby Blake wrote:

 Hi,

 One of our users has recently changed over from having a dual-boot
 win98/Linux machine to a Linux only machine, incorporating a vmware
 windows 98 partition (look at http://www.vmware.com/ for details).  I
 had believed it would be possible to install the retrospect client on
 this windows 98 partitions, just as if it was a 'normal' windows 98
 installation - it has its own IP address and every other aspect of
 networking seems to work OK.

 However, the Retrospect client installs OK but cannot be seen from the
 server - it gives a 541 error "client not installed or not running".
 Can anyone shed any light on this?  The server is 4.3 for Mac and the
 client is 5.1.  Am I being over-optimistic in expecting it to just
 work?

 Thanks
 Toby Blake
 University of Edinburgh

 --
 --
 To subscribe:[EMAIL PROTECTED]
 To unsubscribe:  [EMAIL PROTECTED]
 Archives:http://list.working-dogs.com/lists/retro-talk/
 Search:  http://www.mail-archive.com/retro-talk%40latchkey.com/

 For urgent issues, please contact Dantz technical support directly at
 [EMAIL PROTECTED] or 925.253.3050.



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:http://list.working-dogs.com/lists/retro-talk/
Search:  http://www.mail-archive.com/retro-talk%40latchkey.com/

For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.



Backup Script settings

2000-12-13 Thread Ben Mihailescu

Hi all,

If I have a script that is suppose to finish at 9:00 am, but it didn't
have a chance to go around all the clients yet, can I ask it (
interactively or through script ) to continue until it picked up all the
clients, or to go let's say another 1.5 hours?

Here are my specs:

Here is my hardware: PIII 733, 512MB RAM, 2 x 30GB HDD, Quantum DLT 4000
SCSI
Tape Drive. (2nd Quantum DLT 7000 to come sooon)

I use Retorspect 5.15 Backup Server with Retro 5.15 Win Clients and 4.2a

Mac clients.


--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering
McGill University, Montreal, Canada
514.398.7467




--
--
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.



Backup configuration help

2000-11-23 Thread Ben Mihailescu
Hi all,

We have quite a few clients to back up in a window of about 14 hours every
night. Currently I am running a single script, that picks up every client
during the night, for the duration of one month. Evidently, the catalog is
getting quite big and towards the end of the month, the process of matching
is quite slow, thus from the 20th of each month, not all clients are reached.
I was wondering if splitting the backup in 3 scripts - let's say for client
A-H, I-R, S-T, and schedule those accordingly throughout the night would
be a viable solution. Of course, this 3 sets would have to be backed up to
he same tape. Is this possible?

I am open to any suggestions, since this is becoming quite a pain. New hardware
is out of the question for now, and I would like to not have to start new
sets every 2 weeks or so, since it involves me coming in on the weekend

Thanks, Ben
-- 
Ben Mihailescu
System Administrator
Electrical and Computer Engineering
McGill University, Montreal, Canada
514.398.7467






--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:

For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.


Re: Backup configuration help

2000-11-23 Thread Ben Mihailescu
I'm not sure I understand your suggestion.
To run a full bu it takes about 3 DLT4000 tapes (approx. 90GB). I only have
one DLT drive, and during the initial full backup I have to come in twice
to change tapes. It would be nice to have another two drives
If I misunderstood, sorry, but please explain.

Thanks, Ben


Dan O'Donnell wrote:
As you point out, it appears that the size of the catalog is the 
bottleneck. Changing the cycle from 1 month to 2 weeks (approx.) 
would be better, but why do you have to set it up to change on a 
weekend. Why not set it to break on the Monday following the weekend, 
or some other arrangement that is convenient?

  
At 9:11 AM -0500 on 11/23/00, Ben Mihailescu wrote:

  Hi all,
We have quite a few clients to back up in a window of about 14 hours 
every night. Currently I am running a single script, that picks up 
every client during the night, for the duration of one month. 
Evidently, the catalog is getting quite big and towards the end of 
the month, the process of matching is quite slow, thus from the 20th 
of each month, not all clients are reached.
I was wondering if splitting the backup in 3 scripts - let's say for 
client A-H, I-R, S-T, and schedule those accordingly throughout the 
night would be a viable solution. Of course, this 3 sets would have 
to be backed up to he same tape. Is this possible?
I am open to any suggestions, since this is becoming quite a pain. 
New hardware is out of the question for now, and I would like to not 
have to start new sets every 2 weeks or so, since it involves me 
coming in on the weekend



--

--

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.









--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:

For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.


Re: How can I stop an NT service before backup?

2000-10-31 Thread Ben Mihailescu

How about you run an AT job with "net stop service" before your backup starts
and then you run an AT job with "net start service" after retrospect is done.

HTH, Ben

"Kraut, David" wrote:

 I have a backup job that backs up several servers during the night.  One of
 these servers has a SQL database that will not back up properly unless the
 NT SQLBase service is stopped first.  I went thru the support docs and they
 all talk about external scripting?  Is there a simple way that I can stop a
 Windows NT service prior to backup of this server and then start it up again
 after backup.  I know about the "net stop service" command but have no clue
 how to implement within retrospect.  Also, I'm backing up 10 servers in this
 script so it would best if I could stop this service immediately before
 backing the SQL server and then start the service immediately after backup
 of this server is complete.  Sometimes my backup jobs run into the morning
 hours so I can't afford to have this service stopped during the entire
 script.

 Any ideas??

 TIA!!

 David

 --
 --
 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.



--
--
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: Mac Client Uptdate - for Irena

2000-10-19 Thread Ben Mihailescu

Hi James,

I completely understand the Windows side of the client update. If you run the
update with the manual reboot client the old version will still be active until
after the first reboot. I've updated 59 clients last night before my nightly
backup with the manual reboot client (Win) and they have all been backed up
correctly over night.
So, Dantz, it would be nice to put the Mac Client Update software in a
"Macintosh Manual Reboot" folder, rather then just "Macintosh". Essentially it
would have avoided us having this discussion, and therefore be more
efficient.

Cheers, Ben

James Keagan wrote:

 I think what Irena was trying to say is that you must manually restart the
 Mac clients before the change takes effect.  The Windows clients have two
 separate .rcu files: one that will automatically restart the computer and
 one that requires a manual reboot.  And correct me if I'm wrong, but doesn't
 the Windows client service completely stop until reboot, while the Mac
 client can continue operating even if there has not been a reboot (it will
 still be the same version, though)?

 J.

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
 Of Ben Mihailescu
 Sent: Wednesday, October 18, 2000 2:26 PM
 To: retro-talk
 Subject: Re: Mac Client Uptdate - for Irena

 Hi Irena,

 Will they reboot automatically upon installation of the update, or they can
 be
 restarted manually? We are talking about Mac clients only. Your answer was
 great, but ambiguous. Sorry :-(

 Thanks again, Ben

 Irena Solomon wrote:

  Hi Ben,
 
  Yes, Mac clients must be restarted for the updated client software to load
  and run.
 
  Irena Solomon
  Dantz Development Corporation
  925.253.3050
  [EMAIL PROTECTED]
 
   From: Ben Mihailescu [EMAIL PROTECTED]
   Organization: McGill University
   Reply-To: "retro-talk" [EMAIL PROTECTED]
   Date: Wed, 18 Oct 2000 12:43:39 -0400
   To: Retrospect List [EMAIL PROTECTED]
   Subject: Mac Client Uptdate
  
   Hi all,
  
   If I embark on updating all the Mac clients over the network, do the Mac
   clients need to be restarted, like the Windoz ones?
  
   Ben
  
   --
   Ben Mihailescu
   System Administrator
   Electrical and Computer Engineering, McGill University
  
  
  
  
   --
   --
   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.
 
  --
  --
  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.

 --
 Ben Mihailescu
 System Administrator
 Electrical and Computer Engineering, McGill University
 514.398.7467

 --
 --
 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.

 _
 Do You Yahoo!?
 Get your free @yahoo.com address at http://mail.yahoo.com

 --
 --
 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.

--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering, McGill University
514.398.7467




--
--
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.



Mac Client Uptdate

2000-10-18 Thread Ben Mihailescu

Hi all,

If I embark on updating all the Mac clients over the network, do the Mac
clients need to be restarted, like the Windoz ones?

Ben

--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering, McGill University




--
--
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: Mac Client Uptdate

2000-10-18 Thread Ben Mihailescu

Does this happens automatically, or can I have an option to restart manually
like the Win boxes?

Thanks, Ben

Irena Solomon wrote:

 Hi Ben,

 Yes, Mac clients must be restarted for the updated client software to load
 and run.

 Irena Solomon
 Dantz Development Corporation
 925.253.3050
 [EMAIL PROTECTED]

  From: Ben Mihailescu [EMAIL PROTECTED]
  Organization: McGill University
  Reply-To: "retro-talk" [EMAIL PROTECTED]
  Date: Wed, 18 Oct 2000 12:43:39 -0400
  To: Retrospect List [EMAIL PROTECTED]
  Subject: Mac Client Uptdate
 
  Hi all,
 
  If I embark on updating all the Mac clients over the network, do the Mac
  clients need to be restarted, like the Windoz ones?
 
  Ben
 
  --
  Ben Mihailescu
  System Administrator
  Electrical and Computer Engineering, McGill University
 
 
 
 
  --
  --
  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.

 --
 --
 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.

--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering, McGill University
514.398.7467




--
--
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: Mac Client Uptdate - for Irena

2000-10-18 Thread Ben Mihailescu

Hi Irena,

Will they reboot automatically upon installation of the update, or they can be
restarted manually? We are talking about Mac clients only. Your answer was
great, but ambiguous. Sorry :-(

Thanks again, Ben

Irena Solomon wrote:

 Hi Ben,

 Yes, Mac clients must be restarted for the updated client software to load
 and run.

 Irena Solomon
 Dantz Development Corporation
 925.253.3050
 [EMAIL PROTECTED]

  From: Ben Mihailescu [EMAIL PROTECTED]
  Organization: McGill University
  Reply-To: "retro-talk" [EMAIL PROTECTED]
  Date: Wed, 18 Oct 2000 12:43:39 -0400
  To: Retrospect List [EMAIL PROTECTED]
  Subject: Mac Client Uptdate
 
  Hi all,
 
  If I embark on updating all the Mac clients over the network, do the Mac
  clients need to be restarted, like the Windoz ones?
 
  Ben
 
  --
  Ben Mihailescu
  System Administrator
  Electrical and Computer Engineering, McGill University
 
 
 
 
  --
  --
  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.

 --
 --
 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.

--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering, McGill University
514.398.7467




--
--
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: Mac Client Uptdate - for Irena

2000-10-18 Thread Ben Mihailescu

Hi Irena,

Thanks, that's good news. Sorry if I seemed harsh. It's better to be clear than
sorry.

Cheers, Ben

Irena Solomon wrote:

 Hi Ben,

 They will require a manual reboot; Retrospect won't automatically reboot a
 Mac client after updating.

 Thanks for keeping me in check ;)

 Irena

  From: Ben Mihailescu [EMAIL PROTECTED]
  Organization: McGill University
  Reply-To: "retro-talk" [EMAIL PROTECTED]
  Date: Wed, 18 Oct 2000 17:26:16 -0400
  To: retro-talk [EMAIL PROTECTED]
  Subject: Re: Mac Client Uptdate - for Irena
 
  Hi Irena,
 
  Will they reboot automatically upon installation of the update, or they can be
  restarted manually? We are talking about Mac clients only. Your answer was
  great, but ambiguous. Sorry :-(
 
  Thanks again, Ben
 
  Irena Solomon wrote:
 
  Hi Ben,
 
  Yes, Mac clients must be restarted for the updated client software to load
  and run.
 
  Irena Solomon
  Dantz Development Corporation
  925.253.3050
  [EMAIL PROTECTED]
 
  From: Ben Mihailescu [EMAIL PROTECTED]
  Organization: McGill University
  Reply-To: "retro-talk" [EMAIL PROTECTED]
  Date: Wed, 18 Oct 2000 12:43:39 -0400
  To: Retrospect List [EMAIL PROTECTED]
  Subject: Mac Client Uptdate
 
  Hi all,
 
  If I embark on updating all the Mac clients over the network, do the Mac
  clients need to be restarted, like the Windoz ones?
 
  Ben
 
  --
  Ben Mihailescu
  System Administrator
  Electrical and Computer Engineering, McGill University
 
 
 
 
  --
  --
  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.
 
  --
  --
  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.
 
  --
  Ben Mihailescu
  System Administrator
  Electrical and Computer Engineering, McGill University
  514.398.7467
 
 
 
 
  --
  --
  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.

 --
 --
 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.

--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering, McGill University
514.398.7467




--
--
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.



OS9 and Retrospect 4.3

2000-10-10 Thread Ben Mihailescu

Hi all,

I just installed Retrospect 4.1 + 4.3 upgrade on a Performa 6360 running
OS9. Everything seems to be OK, the only problem is that when I go to
Devices, I see the following line for my Quantum DLT4000 SCSI drive:

ID #2Quantum DLT4000CCIE(no driver)

I gather my Mac can see the drive, but Retrospect is not loading the
driver for it?
If anyone has had the same experience, maybe you can share the fix.

TIA, Ben




--
--
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: changing client password?

2000-08-29 Thread Ben Mihailescu

From your backup server go to the Configure tab, click Clients. Choose
your client pc and under the tools tab use the Set Password option. On
the client side I don't think there's an option for changing the
password.

HTH, Ben

andrew wrote:

 Client 5.1:  is there any way to change the password...short of
 re-installing the client?

 --
 --
 To subscribe:[EMAIL PROTECTED]
 To unsubscribe:  [EMAIL PROTECTED]
 Archives:http://list.working-dogs.com/lists/retro-talk/
 Problems?:   [EMAIL PROTECTED]

--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering, McGill University
514.398.7467




--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:http://list.working-dogs.com/lists/retro-talk/
Problems?:   [EMAIL PROTECTED]




Retrospect Error Messages

2000-08-09 Thread Ben Mihailescu

Hello all,

I run a nightly backup using Retrospect 5.11 on a Win2k Server machine
(member server only). I backup a mixed (Mac and Win) bunch of clients.
Generally backups are going good (no major errors), yet I get sometime
error 1017 - insufficient permissions on some of the Mac files. Nothing
has changed on the clients from a permission prospective and
applications are closed. I looked through the error messages posted on
the web by Dantz and read the manual, yet I didn't find anything about
this error message.
Did anybody experience this before? Any clue what *exactly* it means in
terms of fixing it?

Thanks, Ben

--
Ben Mihailescu
System Administrator
Electrical and Computer Engineering, McGill University
514.398.7467




--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:http://list.working-dogs.com/lists/retro-talk/
Problems?:   [EMAIL PROTECTED]