Author tim.golden
Recipients Lachlan.Kingsford, steve.dower, tim.golden, zach.ware
Date 2014-10-27.09:04:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <544E0AAF.7010101@timgolden.me.uk>
In-reply-to <1414392827.56.0.571948062757.issue22739@psf.upfronthosting.co.za>
Content
I very much doubt that this is a Python issue as such.

Other things being equal, I would expect Harddisk\DR1 to be a CD-ROM or
some other removable disk. Using something like winobj.exe from
sysinternals should show what it expects to be on a given machine. It's
certainly possible that the machine on which cx_freeze is being used has
a permanent D: drive while the corresponding drive on the target machine
is removable.

(Strictly Harddisk\DR1 needn't be the D: drive and it needn't be
removable, but that's far and away the most common configuration).

I obviously can't say why any code should be be trying to access that
drive. You could try running procexp.exe (sysinternals again) to see
what handle is being attempted on that drive by that program which might
lend a clue as to where the problem is arising. But, again, I don't
believe this is a Python issue.
History
Date User Action Args
2014-10-27 09:04:51tim.goldensetrecipients: + tim.golden, zach.ware, steve.dower, Lachlan.Kingsford
2014-10-27 09:04:51tim.goldenlinkissue22739 messages
2014-10-27 09:04:50tim.goldencreate