Maxx2206

Hi, among the things i always disliked about OFP and ArmA was that certain GUI elements werent configurable easily and/or lacked any form of convenience. one of these things being the ingame text chat. both, the chat buffer (position, scrolling, size, maybe "fade" timer) and the text input field (position, some more edit functions like a real working cursor) really could need some loving. i hope you devs might consider spending a little time on the text chat as soon as the main bug fixing and feature adding is cooling down. btw. right now its already quite annoying that the chat buffer is drawed over the input field, which makes half of your current input barely visible until you hit enter - just to realize it was the wrong chat channel and you have to start over since theres barely any decent convenient features supporting easy chatting.

hi, ok, try not to mix up things.. i dont remember anyone talking about the /3gb parameter in boot ini at all tbh. the original troubleshoot post (refer to the 64bit faq) was about using msconfig to set the maximum ram there. my post was about the same, just by using the new bcdedit (aka boot.ini replacement of vista). the /3gb parameter indeed is different to the max ram options, which is btw. the recommended way to debug applications for memory issues and low memory system compatibility. oh, and saying there are no performance differences at all is wrong, too. there are apps that wont show any significant difference as well as apps that will greatly benefit from it. the latter ones are usually very specialized apps/tasks tho, e.g. plugins, effects and filters in video and image processing applications. other apps *might* or might not benefit from it, but thats not really a good reason not to evolve tbh . but thats a whole different story... right now and here it's ArmA and its compatibility with 64bit systems we're talking about. and seeing how queens gambit results in 100% CTDs all the time while the unmodded ArmA at least seems to run ok here (with 3gig as well as 4) indicates its not all the OS' fault. ps. 32bit windows doesnt necessarily use the 3120mb ram you mentioned. it is true that win32 (vista and xp alike) cant utiolize the full 4gig, but the actual amount depends on various things. most of all its the gfxmem and the various shadowing/memory mapping options of the mainboard. you can end up with anything from 3gig up to roughly 3.7gig effective ram on a 32bit windows. my config resulted in 3.5gig with 32bit bit vista and xp (where arma still ran fine most of the time).

Hi, ok, odd things start to happen here and from what i can see it is not the commonly known/reported 4gb ram problem. the first time i installed and launched arma since i replaced my xp32/vista32 dualboot system with a pure vista64 one was after i purchased queens gambit. the game at first didnt even start properly. it showed blocky lowres graphics, the icons (multiplayer, options, exit etc) were just black squares and so. i restored my old arma config which i backed up prior to setting up the new sysetm and arma launched ok again. then i wanted to try the new campaign royal flush... it started loading, the first intro movies started and it seemed to run ok, but when the intro was about to end and the actual game about to start i found myself on the desktop - arma had crashed. i tried it a few times and it was always the same. seeing all the reports about vista64 and 4gig ram i thought this might be the reason. since i didnt like the masconfig method i started learning how to use bcdedit to make different boot configurations comparable to those you could do in the boot.ini on xp. it was surprisingly easy, so i made a 3gig configuration and tried it again... the result was the same.. intros playing well, crash to desktop when the game would start for real. interestingly, when i launched arma with the old unmodded icon i could resume my old campaign savepoint there and play the mission without any crash. so at this point it appears to be limited to the queens gambit mod for some reason. also, i never had this bluescreen some people are reporting, just the crash to desktop. currently using the latest beta drivers 163.75 on a 8800gts 320mb, amd x2 5200+ EE and vista home premium 64bit. any ideas or similar issues? ps. for those interested in the boot config creation: it takes aless than 2 minutes and only 3 steps to create your own boot menu under vista. vista stores boot information in memory rather than in a boot.ini nowadays. manipulation is done using the bcdedit.exe commandline tool and it follows some rather simple rules. you can create/edit/delete any number of new configs and set the display order, the display order also affects the standard selection. the only little annoying thing is that working with boot configs requires you top specify a unique ID all the time to tell bcdedit which iof the entries you want to work with. 1. open your commandline (start->execute->"cmd"). type to view the standard setup. notice the 2nd set of data which shows {current} as identifier. this is the default configuration and any other config you will create will show a rather long ID instead of "current" <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">bcdedit /copy {current} /d "Insert the name of the config you create here" this creates a copy of the standard boot configuration with the new description (what its called in the menu) you entered after the /d flag. oh, and and the "curvy brackets" are not a mistake, you need to enter those exactly that way. now type again "bcdedit" and you will see the result. it will show 2 entries now, one with the ID current, one with a very long alphanumeric ID. 2. by using right-mouse and mark, you can mark this new ID (right click, select mark, then mark the id by a continuous leftclick+drag, when done right click on it again to copy it to clipboard - not very convenient, but thats how the commandline copy/paste works) and enter the following: vista knows 2 ways to limit memory size (originally for development and debugging purposes). removemmemory <megabytes>: removes/disables the specified amount of ram truncatememory <bytes>: removes/disables any ram higher than the specified amount 3. as a final step, since the default boot timer is set to 30 seconds which is a bit much, reduce it using or any value you prefer.reboot your system and enjoy your xp-style bootmanager menus under vista. no need for the more advanced options at this place unless someone has any concrete questions i guess.

hi, i used to play arma with 4gig installed on xp home 32bit and vista home premium 32bit. of course, depending on the actual system only about 3.5gig were actually really used. but at least it worked. whats the exact use of the disable command youre mentioning here? im just curious because i just replaced my dualboot xp/vista 32bit with a fresh and clean vista64bit system and started having issues with arma now (still 4gig ram installed).

hi, im just wondering if we will ever see an arma patch which gets rid of the disk-check some day like bis did for older OFP released back in the good old days. i understand that "checking" games that come with plain install keys is a must for a certain time but people nowadays get used to titles where this isnt necessary anymore - be it because of unique ids, internet activated accounts or similar mechanisms. as a veteran ofp player (bought the first copy right on the release day, bought all the addons individually and got me another GOTY edition just in case i want to play here in the home lan) i vividly remember when the first patch has been released which didnt require the original disk anymore - that was a very welcome patch. i love arma, but seriously, i wished it would have a different player-id mechanism which wouldnt require the disk anymore (including your need to write disk check routines, update the copyprotection with every other update and so on) and instead would give you more time closing all the many "security holes" which make arma a real playground for all kinds of cheaters these days.

I had a quick look at doing so, but i think the sata / raid is causing an issue. I need to sit down and have a fiddle with it. hi, why would the sata/raid prevent you from doing this if you already considered it? just make sure you get all the xp drivers for your hardware and from the chipset driver package extract the plain sata/ide/raid drivers to a separate floppy. most chipsets even have their own makedisk tool for that. i just downgraded a brand new vista machine down to xp home for a m8 this way and it worked like a charm. most sata setups work out of the box with any sp2-patched xp install disk. some rare chipsets and most raid setups just need the floppy disk and require pressing f6 during the inital boot. anyway, sounds like im lucky or something since i run xp+vista on a dualboot machine and i can play arma on either os (nforce 570sli, 8800gts running xp home sp2 and vista home premium 32bit with the microsoft hotixes and latest nvidia drivers)