minitotoro <[EMAIL PROTECTED]> wrote:
>
>Upon further investigation it turned out to be a windohs 64-bit issue
>(which is what I was afraid of). I did however find an asinine work
>around.
>
>Make a copy of defrag.exe from the system32 folder and paste it in the
>same directory as the python script
On May 2, 4:15 pm, minitotoro <[EMAIL PROTECTED]> wrote:
> On May 2, 3:46 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
>
>
>
> > minitotoro wrote:
> > > On May 2, 3:07 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
> > >> [EMAIL PROTECTED] wrote:
> > >>> I have a script that runs fine in Windows 2003 (32
On May 2, 3:46 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
> minitotoro wrote:
> > On May 2, 3:07 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
> >> [EMAIL PROTECTED] wrote:
> >>> I have a script that runs fine in Windows 2003 (32-bit). It basically
> >>> calls the Windows defrag command. When I try th
minitotoro wrote:
> On May 2, 3:07 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] wrote:
>>> I have a script that runs fine in Windows 2003 (32-bit). It basically
>>> calls the Windows defrag command. When I try the exact same code on
>>> Windows 2003 (64-bit) I get the following m
On May 2, 3:07 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > I have a script that runs fine in Windows 2003 (32-bit). It basically
> > calls the Windows defrag command. When I try the exact same code on
> > Windows 2003 (64-bit) I get the following message:
>
> > C:\Scr
[EMAIL PROTECTED] wrote:
> I have a script that runs fine in Windows 2003 (32-bit). It basically
> calls the Windows defrag command. When I try the exact same code on
> Windows 2003 (64-bit) I get the following message:
>
> C:\Scripts>autodefrag.py
> Starting defragment: defrag -v C: >>c:/Script
