Author Topic: Read errors  (Read 2718 times)

rebootedrock

  • Posts: 1
  • Turrets: +0/-0
Read errors
« on: April 11, 2007, 12:56:10 am »
Getting some strange read/exec errors on my windows machine when trying to use the server.
Code: [Select]
2080 files in pk3 files
execing default.cfg
execing autogen.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
...detecting CPU, found generic

------- Input Initialization -------
No window for DirectInput mouse init, delaying
Joystick is not active.
------------------------------------
--- Common Initialization Complete ---
Winsock Initialized
Opening IP socket: localhost:32123
Hostname: tardis
IP: 192.168.1.136
Working directory: C:\Program Files\Tremulous
couldn't exec server.cfg
Hitch warning: 4066066 msec frame time

It fails to exec the server.cfg file and the autoexec.cfg file for some reason.
Before you tell me, I re downloaded these files 3 times, reinstalled tremulous twice and tried fresh and also modded .cfg files. Nothing Works.
I am following the guide for a win machine at the top of the page(exactly  :cry: ) and dont have any idea whats wrong. All the files are in the right place, all the files are fresh and supposed to work, only the server says that it still tastes like garbage :((.

kevlarman

  • Posts: 2737
  • Turrets: +291/-295
Read errors
« Reply #1 on: April 11, 2007, 06:40:35 am »
none of those errors are fatal, unless there's some other error you didn't copy, you probably just forgot to tell the server to start a map
Quote from: Asvarox link=topic=8622.msg169333#msg169333
Ok let's plan it out. Asva, you are nub, go sit on rets, I will build, you two go feed like hell, you go pwn their asses, and everyone else camp in the hallway, roger?
the dretch bites.
-----
|..d| #
|.@.-##
-----

next_ghost

  • Posts: 892
  • Turrets: +3/-6
Read errors
« Reply #2 on: April 11, 2007, 08:57:25 am »
There's a list of directories searched by Tremulous for files. Put the .cfg files in one of them.
If my answer to your problem doesn't seem helpful, it means I won't help you until you show some effort to fix your problem yourself!
1.2.0 release's been delayed for 5:48:00 already because of stupid questions.