 | | | Python plug-in raising erros heck knows why - SOLVED, but... | Python plug-in raising erros heck knows why - SOLVED, but... 2005-06-04 - By kim aldis
Back
It was me, I'd trash all my drive mappings and work exclusively with unc.
The only disadvantage I'm aware of is the default DOS doesn't allow you to
CD to a unc directory and this can give problems with some startups. There's
a registry hack that will absolve this but I use a Cygwin shell which
doesn't care.
kim@(protected)
kim@(protected)
> -- --Original Message-- --
> From: owner-xsi@(protected)
> [mailto:owner-xsi@(protected)] On Behalf Of Bernard Lebel
> Sent: 03 June 2005 18:24
> To: XSI@(protected)
> Subject: Re: [script] Python plug-in raising erros heck knows
> why - SOLVED, but...
>
> Oh yeah. Here is an example: I imported a model. Then I check
> the source paths.
>
> First half: file path is UNC, resolved path is the mounted drive.
> Second half: file path is mounted drive, resolved path is UNC.
>
> Impossible to change this, either by manually recreating the
> clips or by script.
> Go figure.
>
>
> Bernard
>
>
>
> On 6/3/05, kim aldis <kim@(protected)> wrote:
> >
> >
> > there are some fairly hideous issues with mapped drives and
> unc paths.
> > Xsi still, occasionally, seems hell bent on reverting unc
> paths back
> > to drive maps if it catches the slightest wiff of a mapped
> drive. best
> > to stick with either one or the other. It's the mixing that
> causes the problems.
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following
> text in body:
> unsubscribe xsi
>
>
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
|