-
david_costanzo committed patchset 177 of module pak0 to the Open Quartz CVS repository, changing 1 files.
2006-11-23 09:30:22 UTC by david_costanzo
-
david_costanzo committed patchset 176 of module pak0 to the Open Quartz CVS repository, changing 1 files.
2006-11-23 09:28:20 UTC by david_costanzo
-
david_costanzo committed patchset 131 of module utils to the Open Quartz CVS repository, changing 1 files.
2006-11-12 03:06:41 UTC by david_costanzo
-
david_costanzo committed patchset 175 of module pak0 to the Open Quartz CVS repository, changing 1 files.
2006-11-12 03:04:13 UTC by david_costanzo
-
david_costanzo committed patchset 174 of module pak0 to the Open Quartz CVS repository, changing 1 files.
2006-11-12 02:59:35 UTC by david_costanzo
-
david_costanzo committed patchset 173 of module pak0 to the Open Quartz CVS repository, changing 42 files.
2006-11-10 06:44:29 UTC by david_costanzo
-
david_costanzo committed patchset 172 of module pak0 to the Open Quartz CVS repository, changing 42 files.
2006-11-10 01:21:10 UTC by david_costanzo
-
Logged In: YES
user_id=109252
I have checked in a fix for this. I don't think there is a
need to release the fix, because I don't think this bug was
present in any released files. But if you did sync-up to
CVS and had this problem, try re-syncing.
2006-11-10 00:39:57 UTC by david_costanzo
-
david_costanzo committed patchset 130 of module utils to the Open Quartz CVS repository, changing 4 files.
2006-11-09 19:26:39 UTC by david_costanzo
-
The build outputs corrupt PAK files on Windows. The
Quake engines do their best to load the file and don't
emit clear diagnostics. The result is Quake simply
doesn't run with the PAK files that user's build on
their own.
The root cause of the problem is that par.c assumes
that off_t is a four byte value. On my Windows box and
with my version of gcc, off_t is an eight byte value...
2006-11-09 19:04:20 UTC by david_costanzo
