QuattroGam3r

You need to change the default dash in Dashlaunch. Open the Dashlaunch installer and point it to the new Aurora path where the old one is listed. If you replaced your Aurora folder with your new one, how do you expect it to run the old one?? You can't run Windows 7 once you upgraded to Win10, can you? You may be better off deleting the old Aurora installation rather than Copying over it, you may have old files from 0.1 still in there. I would personally start fresh by deleting anything Aurora, then putting a fresh Aurora install in and pointing dashlaunch to it. Also, maybe you can share what version Dashlaunch and kernel your running. You may be a bit out of date there. Here is an example of dashlaunch-->

No! No piracy here. Be glad to help you with your Aurora issues though.

http://marketplace.xbox.com/en-US/Product/Fable-III/66acd000-77fe-1000-9115-d8024d5308d6 or http://www.amazon.com/Fable-Limited-Collectors-Edition-360-Xbox/dp/B002I0H7U6

Then that would most likely be your issue, not sure where that base version came from. Unfortunately, I don't think it's allowed to share xex files here (or give links to them). You may be on your own there, but there are a few sites out there that have just xex's for games. You just need to search for them. Worst case, get yourself another copy of the game with a known base version. edit: it could be a modified xex, maybe??

Maybe try a legitimate source. edit: BTW, if you're still running XEXmenu, my guess is that your whole system is way behind in updates. What kernel are you currently running? This game needs minimum kernel version 13599. Maybe update to 17489 (and Dashlaunch 3.16) and install something a little newer like Aurora, or at least the abandonware FSD3. Lots of good info on this site to get you up to date. Maybe also next time, don't go advertising that you're pirating games. Piracy is not condoned or tolerated on this site and besides being warned or possibly even banned, it will almost certainly limit the amount of help you receive.

Thanks, that makes sense. So adding GIF support to Aurora, if it's even possible, sounds like the only solution. I know Team Pheonix wants to keep Aurora as lean as possible, and GIF's use lot's of memory. So Probably out of the question. Kodi uses GIF's for backgrounds on some skins (AeonMQ7 alpha/beta), but these are reserved for higher end systems that can handle the hit without dragging the interface down to a crawl. Matter of fact, they're only recently coming out with support for libgif on 16+ beta builds.

That's interesting, I would have thought it came down to the codecs included in the kernel. I'll go bury my head in the sand now, lmao.

Yeah, I hear what you're saying, it would be nice. But I don't think there's GIF support in the kernel. Maybe Swizzy can correct me if i'm wrong, but I think you're limited to jpg, png, bmp and dds textures.

I believe they are transitions done when you build/edit the skin files in xuitool. edit: you can actually see Felida make a frame transition in one of his vids. So I imagine if you have all the frames of the GIF, you could just plop them down frame by frame.

Is this a typo? I see no TU with that base version on Unity web site. Only Base Version: 00000002 I had a problem updating my TU on this game once before though, I ended up having to swap out my default.xex before it worked properly.

I think someone else had a similar problem with large libraries. He had Aurora on his external hdd. If yours is on external, maybe try moving the installation to internal hdd.

I don't know what your original problem was with missing covers, but in your first post you said you tried to delete Aurora to reinstall. Now you most likely have an incomplete installation because you cannot delete all of Aurora while it's running. You would need to go to a file manager in Dashlaunch, FSD, XEXmenu, or install another Aurora and boot to it before you can delete the old install. edit: you might also want to check if livestrong is enabled in Dashlaunch. If it is, that's why some items are not being scraped for your games. Disable it.

Check if MediaID and TitleID match the game. If not it won't recognize it. Also, if Aurora is not set to scan for title updates on start, you need to select scan now in settings.

Good point about OS X Server. Since it is a separate app it may bundle its own Samba. However that could also be what is stopping SMBup from working. I would think you could still disable Samba shares from the Server app and run it instead from OS X, just to test.

I've read before that ConnectX only works with Samba version 3.6. Maybe this is the reason why only Windows users have been able to connect. Interesting that you have gotten it to work using Linux though, you might be the first, lolz. The key most likely lies in either your logs from the mac refusing the connection, or, as @ravasquez has mentioned before, running wireshark to capture packets. I run OS X also, so i'll help if I can, but to date I don't think anyone has been successful. edit: maybe this might be of some help, it's for an older version of OS X, but using homebrew this guy replaced the Apple SMBX stack with Samba's stack. http://blog.helloyama.com/post/77813860132/replacing-the-os-x-109-mavericks-smb-stack-with I checked with Cakebrew and Samba 3.6.25 is the most current version.

Avatar editor constantly loading is usually because Dashlaunch fake live is enabled. Disable fake live for access to avatar editor. You lost me on the part about no video signal, could you describe what's happening there in more detail.

It's a little out of my realm of experience, But I thought I read about 128MB being usable with the right Bios (5035, IND, etc.). You may also need the correct dash to be able to take advantage of it. I think XBMC v3.3+ takes care of this. To be honest, I would just google "128MB xbox upgrade" and get as much info as you can. Maybe someone else can tell you for sure, but I can't without researching it first. I don't think it matters so much where the bios is, TSOP or Chip, as long as it supports the 128MB mem chip.

NP man. I even got my advice wrong at first if you read my edit. We all make oversights sometimes. Let us know if it fixed it for you.

I would go with the bios on the mod chip personally, that way your TSOP is left alone. Remember though, you're not going to get Slayer's, super disc, hexen, etc. to run until you have either modded the TSOP or installed the mod chip. That's the whole point of modding it, to run copied discs and unsigned code. edit: BTW, I think I have an extra bank switch left over from my X3 chip. Didn't need it cause I use the X3CP. Let me know if you need it. edit2: maybe not, looks like the original used a ribbon cable to some board with a parallel port (i assume for programming) and bank switches.

That'd be one way, another would be to hot swap once you boot on modded console, then setup the drive either through super disc or chimp, etc.

Yeah, I just disconnected my network adapter and it crashes the app on my Win10 Virtual Machine. It looks like Swizzy fixed this about 7 months ago, but that version has not been compiled and released yet. If you want to try compiling it yourself, check his github page. Otherwise you will have to wait for him to release the new version. edit: I tried to compile it, but got an error that I don't know how to get past, lolz.

Just a thought Static, but the dev kits may not need a locked hdd because of the need for teams to swap hdds. Maybe taking a donor hdd from a known working Xbox could yield results in getting it to boot. BTW, did you have a xboxdash.xbe in your hdd when you tried to boot it? I believe it goes in C: root

The spinning wheel may be due to fakelive being set to true in dashlaunch. Check it's set to false and it should fix that issue. Sorry, I would have recommended that after your first post, but you said it ran like a bag of hammers, not that it didn't load, lolz. edit: whoops, I accidentally said nohealth, changed it to fakelive

OK, thanks for the clarification Swizzy

According to this, you still have script data set to applications on your Emulators. That's why you you have xexmenu sitting right next to MAME etc. Remove your emu from the content scanning section and re-add it with the correct script data (Emulators), then we can help you if you still have problems with the way the filter is working. You may also want to remove/re-add Original Xbox and Applications, Atari shouldn't be showing next to Predator. I don't have Emu's on my system, but I have 360, Classic, GOD, and Arcade all set to no script data, then Homebrew set to homebrew script data, and I have no issues with pressing right bumper to show each category completely separate. You can't expect Aurora to categorize your Emu's separately from your applications if you are telling it to see Emu's as applications. edit: You may also want to uncheck autoscan from your "Manage Paths". You have to manually select "Scan Now" whenever you add a new path, but it will help Aurora launch a little faster.