Quake 1 problems (Qrack)

[anannyo]

I am using Qrack because that is the only program that works for me for some reason, heres problem #1 i Can't save games or set new defaults... i go to console i type save game
And it says error could not open save.cfg So yeah i have to reset teh game every single time!!! which gets annoying... #2 When i exit quake the screen get too bright, when i restart the computer it returns to normal but it gets annoying every single time restart, restart, restart!!!

So can some1 please help?

[Baker]

When i exit quake the screen get too bright, when i restart the computer it returns to normal but it gets annoying every single time restart, restart, restart!!!

So can some1 please help?

I can tell you one solution to that part of your problem:

Unzip setgamma in your Quake folder and when you have the problem just double-click setgamma.exe to restore the brightness to normal.

http://icculus.org/twilight/darkplac...setgamma11.zip

[MH]

Did you copy your Quake folder from a CD? It sounds like all of your Q1 files are read-only (been there, done that, took me half way to forever to realise what was wrong...)

[anannyo]

no it isnt read only if it was, i would be reading from notepad or something! i copy from cd it aint working, i download quake shareware and took its save config and it doesnt working, looks like qack cannot open the save config

[R00k]

writeconfig game.cfg will save your cfg to game.cfg
save game will save the singleplayer game as game.sav

Qrack will automatically read config.cfg and/or autoexec.cfg, at startup
but, if you want to load your custom cfg use the console command
exec game.cfg


for your problem #2, use setgamma after u exit OR
just type gamma 1 before u exit

I'm not totally sure why your gamma isnt returned to normal after Qrack exits but this will work in the mean time...

[MH]

I think that might be a 3D card problem. I've also seen it on Q3A if the engine crashes - it doesn't run through the normal exit path and leaves things very significantly brighter. Similar might be happening with QRack.

[anannyo]

Hmmm i shall try

[anannyo]

none of it worked it couldn't write a config or save, it says couldnt write config....

[anannyo]

well any1 got a solution? any1?!

[Baker]

If you copied your files directly from a CD Rom in Windows, they would be readonly automatically.

Type in the console:

writeconfig myconfig

If this works, then somehow you have your files as read-only.

Think about it. No one else has ever reported this type of problem. Your files or folders must be read-only or you are running it directly from a CD Rom or other read-only device.

[MH]

An alternative is that you installed Quake as an Administrator to a folder your currently logged-on account doesn't have write access to. I'm seconding what Baker says - nobody else has this problem. I did see it before myself, and the cause was that all my Q1 files were flagged as read-only, like so:



Could you please check this and confirm that it's not the case before we move on to troubleshooting any further?

[MH]

I guess I owe an apology, as I've just had the very same with a config.cfg that is most definitely not read-only. A wild hunch suggests that something in Windows is maintaining a lock on the file from when it was originally opened at start up, so a simple brute force fix is to force it closed before writing it. The function is Host_WriteConfiguration and the line to add is:

while (_fcloseall ());

Putting it in a while loop just makes double sure that everything is definitely closed before continuing.