Moving files from the main to the win_bbs

[ptaylor2]

While moving files from the main to the win_bbs is running very slow. It's been over 20 mins and it's not not even finish moving the files. If I use the winows file manger it only takes a few seconds to move then to a different directory.
Enter your selection, or X to exit: t

Enter Library name to move/copy file(s) to, or X to exit: win_bbs

Moving file to: WIN_BBS\wg33cd.zip
MAIN\wg33cd.zip

Moving file to: WIN_BBS\vircom.pdf
MAIN\vircom.pdf

Moving file to: WIN_BBS\mbbsv10.zip
MAIN\mbbsv10.zip

Moving file to: WIN_BBS\MBBS625V.zip
MAIN\MBBS625V.zip

Moving file to: WIN_BBS\MBBS625f.zip
MAIN\MBBS625f.zip

Moving file to: WIN_BBS\mbbs625e.zip
MAIN\mbbs625e.zip

Moving file to: WIN_BBS\MBBS625.pdf
MAIN\MBBS625.pdf

[daniel_spain]

ptaylor2 wrote:
> While moving files from the main to the win_bbs is running very slow. It's
> been over 20 mins and it's not not even finish moving the files. If I use
> the winows file manger it only takes a few seconds to move then to a
> different directory.
> Enter your selection, or X to exit: t
>
> Enter Library name to move/copy file(s) to, or X to exit: win_bbs
>
> Moving file to: WIN_BBS\wg33cd.zip
> MAIN\wg33cd.zip
>
> Moving file to: WIN_BBS\vircom.pdf
> MAIN\vircom.pdf
>
> Moving file to: WIN_BBS\mbbsv10.zip
> MAIN\mbbsv10.zip
>
> Moving file to: WIN_BBS\MBBS625V.zip
> MAIN\MBBS625V.zip
>
> Moving file to: WIN_BBS\MBBS625f.zip
> MAIN\MBBS625f.zip
>
> Moving file to: WIN_BBS\mbbs625e.zip
> MAIN\mbbs625e.zip
>
> Moving file to: WIN_BBS\MBBS625.pdf
> MAIN\MBBS625.pdf

that is not a standard "move" process. it is not as easy as moving files to a new directory, it has to delete and update btrieve files per file and remove any tracing anywhere else.

[ptaylor2]

daniel_spain wrote:
> ptaylor2 wrote:
> > While moving files from the main to the win_bbs is running very slow. It's
> > been over 20 mins and it's not not even finish moving the files. If I use
> > the winows file manger it only takes a few seconds to move then to a
> > different directory.
> > Enter your selection, or X to exit: t
> >
> > Enter Library name to move/copy file(s) to, or X to exit: win_bbs
> >
> > Moving file to: WIN_BBS\wg33cd.zip
> > MAIN\wg33cd.zip
> >
> > Moving file to: WIN_BBS\vircom.pdf
> > MAIN\vircom.pdf
> >
> > Moving file to: WIN_BBS\mbbsv10.zip
> > MAIN\mbbsv10.zip
> >
> > Moving file to: WIN_BBS\MBBS625V.zip
> > MAIN\MBBS625V.zip
> >
> > Moving file to: WIN_BBS\MBBS625f.zip
> > MAIN\MBBS625f.zip
> >
> > Moving file to: WIN_BBS\mbbs625e.zip
> > MAIN\mbbs625e.zip
> >
> > Moving file to: WIN_BBS\MBBS625.pdf
> > MAIN\MBBS625.pdf
>
> that is not a standard "move" process. it is not as easy as moving files to
> a new directory, it has to delete and update biebtrve files per file and remove any
> tracing anywhere else.

Maybe adding a new function that runs outside of biebtrve may solve the issue? Using a dos call routine.

[daniel_spain]

ptaylor2 wrote:
> daniel_spain wrote:
> > ptaylor2 wrote:
> > > While moving files from the main to the win_bbs is running very slow. It's
> > > been over 20 mins and it's not not even finish moving the files. If I use
> > > the winows file manger it only takes a few seconds to move then to a
> > > different directory.
> > > Enter your selection, or X to exit: t
> > >
> > > Enter Library name to move/copy file(s) to, or X to exit: win_bbs
> > >
> > > Moving file to: WIN_BBS\wg33cd.zip
> > > MAIN\wg33cd.zip
> > >
> > > Moving file to: WIN_BBS\vircom.pdf
> > > MAIN\vircom.pdf
> > >
> > > Moving file to: WIN_BBS\mbbsv10.zip
> > > MAIN\mbbsv10.zip
> > >
> > > Moving file to: WIN_BBS\MBBS625V.zip
> > > MAIN\MBBS625V.zip
> > >
> > > Moving file to: WIN_BBS\MBBS625f.zip
> > > MAIN\MBBS625f.zip
> > >
> > > Moving file to: WIN_BBS\mbbs625e.zip
> > > MAIN\mbbs625e.zip
> > >
> > > Moving file to: WIN_BBS\MBBS625.pdf
> > > MAIN\MBBS625.pdf
> >
> > that is not a standard "move" process. it is not as easy as moving
> files to
> > a new directory, it has to delete and update biebtrve files per file and remove
> any
> > tracing anywhere else.
>
> Maybe adding a new function that runs outside of biebtrve may solve the issue? Using
> a dos call routine.

you have to run it through btrieve as that is the storage method for the file name, size, uploads, downloads, etc.... as you move it it has to export all that data into the moved file lib then remove it from the exported file library. it also is affected by ms time on the harddrive, i found ther old "stock" 5400 ms drives that shipped with alot of stock xp machines was pretty bad but seagate's 7200 did just fine. my usurper init program for wg3 finished in 312 seconds vs 540 seconds on an older drive. with that said i am not saying your drive is the issue, just one of the things that caused slower move problems on other sysops in the past.