Search the Community

Hi all, me again Now that I've learned how to take screenies on DM (thanks to Aluminumhaste) I wanted to post one that I took but I got an error saying that the image ext that I used was not allowed in these forums, It was .jpg so I changed it to .png and I got the same error again. They're on Photobucket.

I realize this isn't a tech forum, but I know some of you are hardware specialists, so I thought I might get some help and advice. As you may remember from about 18 months ago, I built my own system, including a steam-punk-ish wooden case. For reasons I can't justify now, I went with 32 gb of ddr3 1600 9 9 9 24 ram (Patriot, 4X8gb). Two of the original sticks failed memtest. So I went with just the 16gb, not realizing that I could return the defective memory until about a month ago. I sent the bad memory back to Patriot and they graciously replaced it. However, the replacement memory has two distinct differences from the other two sticks they replaced. First, these sticks have a tall aluminum heat-shield, which the originals did not have. Second, while the originals are stamped 1.6v, these are stamped 1.5v. As I eagerly began to disassemble my case to put these replacement sticks in, I realized they are physically too tall to avoid touching the frame of the large intake fan I have mounted in the floor of my case. The only way to fit them was to trim a quarter-inch of the aluminum heat-shield from the end. Without giving it much though (obviously) I went ahead and did so. Unfortunately, with those sticks installed, my computer goes into a failed boot cycle, where it tries to turn on but cycles itself off again after about three seconds, then on, off, on, off, etc. This happens under any configuration that uses either of the two replacement sticks, whether solo or in conjunction with the other sticks and regardless of which of the four slots they go in. Hmm... Could be defective memory, of course. But I suspect my trim-job of the heat-shield has pretty much made them impossible to return. So my question is this: could this behavior also be caused by some issue with the voltage of the memory? As I said, my original Patriot memory has 1.6v on the sticker, while these replacements say 1.5v. Every other stat is the same...same timing, same speed, same size. Or did they just replace my memory with the wrong kind and I'm screwed for having modified it? My bios does allow me to change dram voltage. I am a newbie at that and do not understand the theory but can follow directions. Yes, I can get away with not installing these sticks at all. My computer has served me well on the 16gb I have been using all along. But since I paid for them, if I can get them to work, I will be happier. What suggestions can you offer? If this could be a voltage issue, is it possible to make different voltage dram place nice together? Or is that a non-starter? If it can be done, what do I set my dram voltage to? I assume I will have to set the bios with the working ram in place, then put the other ram in to see if it works. Here is my system: Motherboard: MSI Z77MA-G45 Processor: Intel i5 2500k 3.3ghz Video card: Geforce GTX 560 Ti OS: Win 7 Pro, 64bit Memory: Patriot DDR3 1600, 9 9 9 24, running 2 of 4 8gb sticks...the two which don't work also are labelled "Viper" which I do not recall on the originals. The "Viper" also say on the package "Designed for Intell 6/7/8 Series Platforms." Thank you.

Thief 1/2 are the only two games binding me to Windows at this point. Though they play on other platforms with WINE, the loadtimes are painful. We're talking upwards of 10 seconds to reload after detection by a guard. Somebody on the TTLG forums plays on a Mac, and I play on Linux. We both have this problem, so it must be a WINE thing. Is there anyone else interested in this that may have the skills to find some sort of solution? Other games like Deus Ex and UT don't have this problem in WINE. I was thinking it may have something to do with the animated loading graphics in the menu. Perhaps I could try disabling them or replacing them with blanks to see if that makes it load faster. Also, T1 doesn't seem to suffer from this nearly as badly as T2 does. I saw on the WINE Wiki that 2D acceleration is lacking. This is what gave me the above idea. Any ideas?

This is a bug that occurs on current (29 Jan 2013, rev. 5694) SVN code. Proposed solutions are in this post. It's probably related to: 0002811: Font loading does not fall back to English http://bugs.angua.at/view.php?id=2811 Reproduction: After changing language to polish and restarting TDM, the following happens: SetupFonts() in idDeviceContext::Init() can't find fonts for polish language. It does not fall back to loading english fonts. Lack of ANY fonts loaded causes a crash while loading GUI (in idDeviceContext::SetFontByScale() exactly). I've attached the stack trace. I have three solutions for this problem: 1. I've attaches a patch (I18N.cpp.patch.txt). However: - it uses a hard coded value "fonts/english", - it requires #str_04127 to be translated properly for all languages with their own fonts - this is actually an advantage, IMHO. 2. I've also attached an alternative patch (DeviceContext.cpp.patch.txt) that solves this problem. It also uses a hard coded value "fonts/english", and is not as good as the first one. 3. Third solution is to require for translation of #str_04127 to be present in all languages that do not have their own fonts. Translations such as Polish have to be fixed. I actually think that the first solution is the best one, because it's the most bullet-proof (no risk of crashes, ever). (I wanted to edit the original issue, but I don't have permission.) stacktrace.txt DeviceContext.cpp.patch.txt I18N.cpp.patch.txt

Personally I think this is the worst idea ever. The Reason forums has LOADS of info and knowledge, built up through years and years. I'm really sad to see it go away, and I can't understand why they've made this decision. https://www.propellerheads.se/forum/showthread.php?p=1579099#poststop

Tonight I did a dist-upgrade on my Debian Wheezy machine. I was perfectly happy with my fully functional gnome 2.x desktop, which had flawless sound and a UI that was exactly tweaked to how I wanted it. Now I end up with Gnome 3 and the pain-in-the-*** that is PulseAudio. These two were precisely why I left my last distribution. After the upgrades, I go to launch TDM and I get no sound. My UI is completely changed. Why do people insist on forcing unwanted software/changes on the user? Before you say "You're using a testing distribution", this will be the only current distro in a year or two. Those of us who prefer Gnome 2 and a functional (ALSA) sound system will be screwed.... or we can stick with a 2.6.32-era distribution. Long story short: Respect the wishes of users. You can keep packages for "gnome2.x" in the repositories along with the Gnome.3x packages which require a broken audio system. That way, everyone is happy. This isn't really directed at anyone in particular, because almost every distro is doing it. Now I'm reinstalling Debian 6, knowing that I will be screwed in a short wile and be forced to use whatever packages someone else decides to deploy across distributions.