[Box Backup-dev] Hello all - win32 client

[Stuart Sanders]

The "free" version of VS 2005 (ie VS Express) has a non-distributable licen=
se.

So to legally distribute anything he compiles he would need to pay for Visu=
al Studio.

Stuart

> -----Original Message-----
> From: boxbackup-dev-admin at fluffy.co.uk=20
> [mailto:boxbackup-dev-admin at fluffy.co.uk] On Behalf Of Nick Knight
> Sent: Friday, 21 July 2006 4:40 PM
> To: boxbackup-dev at fluffy.co.uk
> Subject: RE: [Box Backup-dev] Hello all - win32 client
>=20
>=20
> Hello Chris,
>=20
> This is probably leads to the need for support two platforms!=20
> You can't
> remove personal opinion! Not sure why you cannot distribute binaries
> produced by MSVC?
>=20
> In this day and age 2GB files are not uncommon, so it needs doing - I
> will have a look and assess it.
>=20
> Still trying to compile though and it barfs on no=20
> BoxVersion.h, where is
> this supposed to be or got from.
>=20
> Thanks
>=20
> Nick
>=20
> -----Original Message-----
> From: boxbackup-dev-admin at fluffy.co.uk
> [mailto:boxbackup-dev-admin at fluffy.co.uk] On Behalf Of Chris Wilson
> Sent: 21 July 2006 09:32
> To: boxbackup-dev at fluffy.co.uk
> Subject: RE: [Box Backup-dev] Hello all - win32 client
>=20
> Hi Nick,
>=20
> > Sorry Chris, I am with Gary, the Microsoft devel environment (I use
> > 2003) its toolset is pretty good for debugging, I can't=20
> comment on the
> > inteli-sense in 2005 but I work on 2003.
>=20
> Sorry Nick, I am with GCC, because I can distribute the resulting=20
> binaries. If I developed with Visual Studio and then distributed
> untested=20
> MinGW binaries, what would happen? :-)
>=20
> > Also in my humble view, Microsoft wrote the compiler, libraries and
> OS,
> > so will they not work better together?
>=20
> But they did not write Box Backup, so perhaps they will not work well=20
> together? ;-)
>=20
> Box has always been developed (on other platforms) using gcc.
>=20
> > In fact I would go as far to say that in my days as an embedded
> software
> > engineer, we always wrote for Microsoft ide, then port to=20
> the platform
> > which would have much faster development cycles!
>=20
> > 1. Large file support - verify it is all working
>=20
> It definitely is not. The POSIX APIs used by Box on Windows do not
> support=20
> files over 2 GB, because they don't have a 64-bit file offset.
>=20
> The problem, unfortunately, is to replace ALL the POSIX APIs with
> emulated=20
> replacements using the Windows APi. That will not be easy.
>=20
> > 3. Look at the possibility of Shadow Copy, it looks quite=20
> tricky so no
> > promises! But this looks much needed for the likes of backing up
> > Exchange
>=20
> This will be the first major problem for MinGW - the VSS API is cl
>=20
> > The problem without shadow copy and trying to backup exchange (or
> > similar - point 3 shadow copy) is you have to back an intermediary
> file
> > using ntbackup - or just pulling out the database with exchange
> > shutdown, but the problem with this is the id of the file=20
> changes so I
> > believe box treats it as a new file so doesn't even try to diff??
>=20
> Box will try to diff if a file is replaced by another with the same
> name,=20
> as well as the contents of a file changing. As far as I know,=20
> the ID is=20
> only used to track renamed files.
>=20
> Cheers, Chris.
> --=20
> _ ___ __     _
>   / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
> / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
> \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |
>=20
> _______________________________________________
> Boxbackup-dev mailing list
> Boxbackup-dev at fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev
> _______________________________________________
> Boxbackup-dev mailing list
> Boxbackup-dev at fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev
>