QUOTE(Bad_Ad @ Sep 1 2010, 01:59 AM)

It wasnt a case of donating when its done, it was a case "If im going to donate now, are you still going to fix it and maybe add XYZ".
Okay, sorry for the misunderstanding. xm360 is still getting bug fixes/features, *especially* ones reported or requested by donators. I'm driven by making sure that people who donated are rewarded.
QUOTE(danthaman673 @ Sep 1 2010, 02:10 AM)

I was wondering where you say in the readme.txt 'I have scheduled a /x /d at midnight' Do you mean server does it automatically because it's in the code?
Or are you referring to having scheduled on the task scheduler thingy, ie; a simple batch that runs the switches whilst the FTP server runs ..
Does the switch/scrape run as separate process? and is there any danger in having multiple instances running (I wonder as I might run it on a server that happens to be mission critical to the rest of my network)
Brgds/Dan
Dan, I schedule the tasks to run at midnight via the OS, it isn't built into xm360_server. They are separate processes (so, all 3 are running at the same time around midnight - the server running 24/7, xbla d/l, and dlc d/l). There is no danger in this what-so-ever. Let me explain. The server itself doesn't use the xbla.csv, or dlc.csv for anything at all. It only delivers them to 360s when they connect if they have been updated. So, even though you happen to be launching xm360_server...the command line parameters cause it to behave entirely differently when you tell it to do the download...and that's the primary reason why it exists as soon as it is finished...so you can leave the OTHER instance running an actual server.
QUOTE(Bad_Ad @ Sep 1 2010, 10:14 AM)

They go in the path you set for HDD + Content
i.e.
hdd = c:\blah\
content = hdd\content
csv would be c:\blah\content\xbla.csv
Right. The issue here is that it must end up somewhere that is mapped as a 360 device...since the 360s fetch it via ftp, it has to appear on one of the "virtual" 360 drives that the server presents to the 360.