Well, that was very supportive of them, wasn't it! :| So what does your php.ini file look like? And is your moodledata folder at the same level as your code directory?
Example (CentOS):
/var/www/html/moodle - is the code directory
/var/www/moodledata - the data directory which is still accessible to apache user/group
Here are some clips from php.ini on a standalone server - not shared
; Maximum allowed size for uploaded files.
; http://www.php.net/manual/en/ini.core.php#ini.upload-max-filesize
upload_max_filesize = 100M
; Maximum size of POST data that PHP will accept.
; http://www.php.net/manual/en/ini.core.php#ini.post-max-size
post_max_size = 100M
The links go to php.net with more technical information concerning.
Change the 100M to whatever size will cover the largest file you have to upload + a Meg or two.
Changes to php.ini on standalone servers require restart of apache service to take affect. Dunno how you do that on a remote shared system.
As far as using File System Repo ... here's how one would set up via command line:
moodledata is located in /var/www/
cd /var/www/moodledata/
mkdir repository
chown apache:apache respository
cd repository
mkdir backups2restore
chown apache:apache backups2restore
*upload the .mbz files to the 'backups2restore' directory.
cd = change directories
mkdir = make a directory
chown = changes the owner/group membership of the directory
On the system I use, the web server runs under apache user and apache group.
One then uses the Moodle Admin interface to create the category/course mentioned earlier and setup the file system repository you turned on. The file system repository would have only 'backups2restore' in the drop down list of physical directories to point towards.
The link given prior actually shows screens.
'spirit of sharing', Ken