Xm360 Version 1.9 (only For Those Who Donated, For Now) Options

[node21]

* If you love XM360, please donate via paypal: xm360donate@gmail.com

CODE

(For those who donated, for now)
Version 1.9 -- Sep 6th, 2010

* Fixed mass ftp transfers freezing
* Fixed size display of GOD titles
* Added ability to push GOD titles
* Added ability to delete LOCAL and REMOTE GOD titles
* Fixed DLC scene being off by 1 pixel
* Fixed Game Saves scene being off by 1 pixel
* Added display of path to bottom of game saves scene
* Fixed gamesave dates in server (sometimes read wrong date)
* Added auto-update from server (previous only handled xm360.xex, now will fetch media directory as well)

CODE

Version 1.8d -- Aug 7th, 2010

* After "ATHiEST" leaked version 1.7b, I stopped work on xm360, except to support people who had donated.  I'm releasing 1.8d to get everyone out there caught up to what has changed since then.  Any future work on XM360 will once again go to people who donated first.  
*
* Due to a request, after unlocking XBLA, you no longer have to do a full re-scan for content
* FTP is much faster thanks to the FSD team teaching me to assign threads to a CPU, go DONATE TO FSD PLEASE!
* Because xm360_server became the only way to update the database, and it doesn't work on linux.  I've gone back to including the perl scrapers (but they are still not as good as xm360_server)

CODE

Version 1.8c -- Jul 15th, 2010

* A suggestion from a donater: The first scene now has the ability to seperate GOD from XBLA (use RB to toggle)
* The server will now wait for you to hit enter after scraping XBLA or DLC
* The server has a new command line option (/Q) to tell it *not* to wait for enter after scraping.  Use this if you automatically scrape every night via a scheduled task, or something like that.

CODE

Version 1.8b -- Jun 27th, 2010

* A request was made to include the DLC filename for missing DLC in the DLC_report.txt

CODE

Version 1.8 -- Jun 27th, 2010

* Fixed fact that you couldn't sort by ratings or raters in the collection manager
* Fixed new scraper (1.7b) getting ratings wrong. I made a change to the file format that breaks compatibility with old xbla_titles.csv, so make sure you are not using an old version of the file.
* Fixed initial scan crashing the 360 if there was no existing content.bin file.
* xm360_server is now aware of the last time xbla_titles.csv and dlc_titles.csv were generated. Every 360 that connects to xm360_server will *automatically* update the xbla_titles.csv and dlc_titles.csv on that 360. Furthermore, you can regenerate, or replace those files without stopping xm360_server from running. So, I leave the server running all the time, 24/7. I have scheduled a /X and a /D every night at midnight as well. It's all invisible without any hands on maintenance. Basically, this feature means you shouldn't ever have to worry about moving these files to your 360 anymore. On the server, these files should be in the same place as content.bin.
* Also, if you put an xm360.xex in that same directory, xm360 will *also* update itself if the version there is newer than the version that is running. It will automatically restart if this happens. This is a moot feature though, unfortunately.

CODE

Version 1.7b -- Jun 19th, 2010
* Fix DLC where multiple DLCs are actually contained in the same file.  They will now display properly, get transfered properly, and get deleted properly.
* Fix ignored DLC not being remembered between session.  I broke this a couple of versions back, I think.
* Changed code so that if you have multiple files queued up, it will only transfer one at a time.  Three at a time was cool, but one at a time is faster.
* Removed the "new unlock" that was in 1.7 until I can get a handle on why it didn't always work.  May be re-introduced later.
* Finally, and maybe most interestingly, the old perl scripts for scraping DLC and XBLA content have been rewritten in C++, and are now included as features of xm360_server.exe

Usage: XM360server.exe /? - list options
       XM360server.exe /D - update or create dlc_titles.csv in the current directory and exit
       XM360server.exe /X - update or create xbla_titles.csv in the current directory and exit
       XM360server.exe /L {locale} - optionally specify the locale (defaults to en-US).  Only useful before /D or /X
       XM360server.exe /U {URL} - optionally specify the URL (defaults to catalog.xboxlive.com).  Only useful before /D or /X
       XM360server.exe - with no parameters runs the server (doesn't exit)

Sample:
XM360server.exe /X  (update XBLA_titles.csv and exit)
XM360server.exe /U catalog.xboxlive.com /L en-US /D (update DLC_titles.csv and exit, URL and Locale specifically overridden)

* One of the key features of this is that it is no longer silent while running.  It will keep you updated on what it is working on.  Sometimes the MS server takes a long time
*   to respond, so it's best to just be patient.
*   Also, the first line of the generated CSV file is now the date that it was run on.  This allows *subsequent* runs to only UPDATE the content that MS says has changed.  This
*   saves CONSIDERABLE time.  XM360 has been modified to accept CSV file either with the date, or without...so old CSV files (or ones generated by the perl scripts) will not break
*   XM360...however, that's only true of version 1.7b and above...anything earlier will choke on a CSV file with a date at the top.

CODE

Version 1.7-- Jun 12th, 2010  (Now released without password for non-donators)

* Add support for remote transfers to the Title Updates and DLC scenes
* xm360 server now also scans for content in \360dashit\Content on hdd1:, usb0:, usb1:, and usb2:
* When repairing DLC filenames, dlc_rename_report.txt is generated in the DLC_REPORT directory. Reminder: You should remember to "rescan all" after a successful "repair" of filenames.
* All scenes now support MASS copying. You get either "GET" everything, "PUT" everything, or "BOTH". In all cases, this will affect only the titles that are shown by the current filter.
** In other words, if you are on the DLC scene, and the <ALL> title is selected, then **ALL** DLC will be sync'd, if Guitar Hero is selected, the only Guitar Hero DLC will be sync'd.
* New values are written when unlocking content. The first four slots are always written to be FF FF FF FF FF FF, FF FF FF FF, and then swapping between 00 00 00 00 and 00 00 00 01.
** This is said to be more universal. I suggest backing up content and trying it out.

**** NOTE: This new unlock code has been removed in 1.7b, so, it's best not to rely on it in 1.7.

CODE

Version 1.6b-- May 30th, 2010

* Because Usb Memory Units (using the new NXE dash) store Title Updates in a seperate partition, I had to add support for a new partition.
* Backups and restores of TUs that are on the USB Memory Unit end up using a Cache2 directory in that same new partition
* XM360server was updated to support defining a path for this new partition (see xm360server.cfg for details), but it's useless for now since xm360 still doesn't support remote TUs
* A request was made to indicate the number of title updates found in cache2 seperately from the regular title updates.
  Both the initial scan, and the status at the bottom of the screen now show the count of "backup" title updates in parens after the regular count
*
* If you love XM360, please donate via paypal: xm360donate@gmail.com

CODE

Version 1.6-- May 29th, 2010

* Xm360 now includes a server component (xm360_server) that runs on the PC.  Find it in the "server" directory of the archive.
* Be sure to define hdd1: in xm360server.cfg before using it.
* This server component when running, allows you to connect to it as if it is another 360 from within xm360.  This allows you to centralize you content on a PC on your network.
* Unlike a regular 360, the server component automatically keeps its content.bin up-to-date when things are pushed to it
* I recommend pushing content to the server from xm360 to begin with to make absoultely certain that it creates the paths correctly on the PC
* xm360 now has very robust FTP job queuing, showing you what's in the queue, and the progress of each transfer right in the content list.
* Due to the fact that you may want to run the server on a port other than 21, XM360 itself now allows you to specify the port in the "Other XBOX" ftp config section.  See XM360.cfg for details.
* Lots of minor fixes in XM360 itself
*
* If you love XM360, please donate via paypal: xm360donate@gmail.com

CODE

Version 1.5c-- May 7th, 2010

* Fixed Passive FTP mode (it was always disconnecting)

CODE

Version 1.5b -- May 3rd, 2010

* Include DLC located on UsbMUx:
* Start all searches at xxx:\\Content\\ instead of xxx:\\Content\\0000000000000000 (game saves)  This means a full scan will take longer, but it's necessary.

CODE

Version 1.5 -- May 2nd, 2010

* Added full support for game saves.  
* Added ability to have the "remote" 360 do a force-rescan when connecting to it.
* Fixed issue where ftp stopped connecting after about 20 or so connections
* Added ability to delete XBLA content on the first page (including REMOTE content)
* Added display of file size to first page
* Added support for UsbMU0: and UsbMU1: if you are using dash 9199 (including via ftp)
* Don't mount DVDROM or FLASH when starting...greatly improves startup time
* Added support for new "REPORT_PATH" in the config which will be used for all reports (XBLA, DLC, GAME SAVES)
* Added filter to the DLC page to show only DLC which wasn't "matched" (or "scraped")
* Added some more specific status messages when connecting to a remote 360
* The local content.bin (file written when you do a rescan all) is automatically updated if you fetch content via ftp or delete local content

** Just a quick note.  Fetching and pushing content still keeps the full path intact.  That means if you are trying to fetch content from a remote memory unit, for example, and you don't have a memory unit locally...it won't work.  It will fail silently.
** Also, pushing content as well as deleting remote content *doesn't* update the remote content.bin.  You should either remember to do a rescan all on that machine the next time you use it, or go to the Remote Connection button, check the Force Rescan checkbox, and reconnect to the remote machine.

This post has been edited by node21: Sep 6 2010, 03:54 PM