Weidman

I figured as much, but I thought I'd throw it out there. Never know when it may come in handy, and you guys are welcome to it. I know it isn't exactly hard to deploy a new machine or just a new server instance, but w/e. Offer goes out to everyone.

Hey 1st MRB. Loved being a part of the battalion years ago. I recently put up a DOD:S server and immediately thought of you guys. I would love to contribute in any way, of course, however atm I am offering up my server for you guys if you'd like to use it for overflow, or to set up a new camp, etc. Whatever use you may have for it. Please contact me on the topic, and I'll be happy to give you access to the server, or configure it however you may prefer. If you'd like to check it out first, of course there is seldom anyone playing on it, but shoot1st.pro is the domain. Happy hunting! - JiKeidan Edit: It's actually shoot1st.pro:27016, as I have a CS:S server running along-side =)

Hello 1st MRB, it's been quite a while since I've made an appearance - few years actually. At any rate, I wanted to let you guys know that I have a server that I maintain myself, and I run a few soft servs on it, 1 of them of course being a DOD:S server. I thought of you guys when I put it up, because for me it's just a toy-around server me and a few friends can play on from time to time... so it has more down time than up time. If you are interested or have use for another server, get in touch with me and I would be happy to give you sftp access to the server so you can modify and control it as you please. Sincerely, Dan Weidman P.S. Hope all has been going well for you boys (and girls)

Hey folks, as many of you may recall, quite a bit over a year ago... perhaps almost 2 years now, I was in the unit. Work and life related circumstances intervened, and I had to leave for a while, and having knowledge of the way I function, I well knew it would be QUITE the while. I have recently moved from Kentucky down to Florida, and am starting my new climbing job down here, so for the time being I am still not free enough to rejoin the unit... but I am working on settling down and with any luck I'll be able to at least be here in support of the 1st MRB! So think of me if you need a computer jockey for some odds and ends bullshamavicks =D For those of you who did not know me before Rec. Weidman came about, I have always gone by [LOC] JiKeidan. LOC is a clan tag that me and a friend made (about around '98), many many years ago, so don't be threatened by it xD. Look forward to seeing everyone in action once again =)... shout out to Candy, and Mullaney (Mullaney of whom i understand is no longer with the unit, but good gal anyhow) and many many others! See you on the battlefield! >=)

For what it's worth, if you hit your "push-to-talk" key while having voice disabled, it automatically re-enables it. Strange though how disabling in-game voice communication caused that noise. Was it loud, as in overpowering in-game sounds?

Name: Dan Weidman Rank: Private Type of issue: Software Brief Description of Issue: Very minute issue, however I'm wondering why I have to log in every time I open the forum... is it possible to "remember user" using a stayalive method in the php library whilst handling cookies or sessions, however it works... I'd rather not speak further on the issue in respect to security, but you get the jist, if you get the jist =) ***Medical Supply Staff ONLY Below this line*** Current Status: Pending Main Technician: J. Candy Supporting Technician: J. Kirk Edit: Please use the MSO Helpdesk form for posts

I'll see what i have time for after i finish writing these articles for the newsroom =P, but i'm usually pretty good with these stuffs =P

Um, I would expect this issue on a custom map download, after some sort of server update texture pack, etc when carrying the same file names as the original textures... or where some sort of server MOD is concerned. However this is colmar... and that's unusual for all kinds of reasons. If you havn't attempted to do any sort of custom textures or otherwise have some sort of program that installed custom skins, models, textures, etc then the only real explanation is within your harddrive or memory. At any rate, regardless of how the files themselves have become corrupted, there is unfortunately only one real fix, redownload the files. You can attempt to "check game file integrity" or whatever it's called, through steam library > right-click DoD:S > properties > local files tab > then "Verify integrity of game cache" but that is just as likely to mess things up even more so. On the other hand, you can delete local content, and re-download all of DOD:S which i've little doubt you've tried, and just hope that steam hasn't screwed up everything on their end - which is likely. If any server admin would have any particularly specific information on the last HLDS update run for the dedicated server, or however they might update their files, then match that information up with the last time you downloaded files, then that would go a long way in determining just what happened, but if the game itself is unaffected, then it's most likely a simple matter of your file md5checksum (provided that's the checking method used by DOD:S) not matching up with the files on the server, or a simple file size mismatch. A lot of servers will not allow access to the game in such a scenario, hence the sv_pure 0 set on the server side. So if trying to join other servers, you are unallowed, that is your reason. Also, if that is not the 1st MRB pub server, and you are attempting to connect to another fairly recently loaded dedicated server, it would likely be that the server you're connecting to is the one not fully updated. When using HLDS to host a dedicated server from either unix or windows, The update has to be run fairly repeatedly until all updates have been obtained. If you're certain both ends are pure to your knowledge... then it is very likely to be hardware related... hdd losing failing sectors, or even memory that is using sectors that aren't quite viable. What THAT means is that basically every file that exists on your system when utilized loads into memory.. but that doesn't mean that the file is closed after loading... often when things are changed around or even just used, it is re-written back into the hdd and then closed. I don't know the source code for DOD:S so it would be difficult to be certain of this... but if your cmos doesn't recognize that your memory is failing and is using bad sectors, and when done with files, the memory is writing information, losing bits at a time back into storage, then it could cause a file mismatch that would be so far behind the scenes, it would cause these issues. Considering the fact that all of the red texted files mentioned are graphical in nature, if you have a video card with it's own memory and GPU, the issue could be there as well... any overclocking you may have done might result in such a situation if the voltages aren't balanced out with the frequencies you clocked up to... or just in general if it's old enough, could be going bad. That's about all the insight I can offer given my lack of knowledge regarding the history of your box. ^.^ But post up what you can on it, the more specific the knowledge the better we can all hone in on the exact issue =) Hope it helps.

Yes sir!

*Salute*

I know I'm new here, but I've spoken with many of you individually as of already, and Giraffe... listening in on your conversations and taking place in them both, I know you know your shit. You got this dude, just remember there is always an information trail and all you need is a single thread Pretty sure with a neck that huge you can see threads for miles xD