View Full Version : winxp + jdoom
April 27th, 2002, 11:14 AM
okay, i know i really already asked this, but figured that maybe i should just be a little more blunt when it comes to asking the question: is anyone out there running v1.13 under xp, and if you are, are you having any problems? just wanting some feedback, if anybody has any... even if it's just to tell me to shut up...
May 5th, 2002, 03:40 AM
What "problems" did you have in mind fiend?
Surely not how to change iwads again!
May 5th, 2002, 03:42 PM
no... in the beginner's guide (which i browsed from the jdoom site), it says that people have reported problems running kickstart under win xp. it doesn't say what problems exactly, and i was just wanting to find out if anyone else was running the newest version of jdoom under xp, and if they were having any problems. see, i just updated my OS, and am still lurking on the sidelines waiting for the most stable version to rear its head.
i'm not having problems b/c i'm not even running it yet. but apparently no one has had these mysterious "difficulties," or no one is running jdoom (w/ kickstart) under xp.
so, i guess i'll just have to cross my fingers.
May 6th, 2002, 08:13 AM
Sorry to tell you that I have absolutely no problems with JDoom on XP...only thing is that I can't connect to a JDoom server hosted in the same LAN...I wonder however this comes http://forums.newdoom.com/UBB/smile.gif
KDX - THE KING DOOM EXPERIENCE
May 6th, 2002, 03:19 PM
at last! thank you, King. that's what i've been wanting to hear, cos i panicked just a bit after i read that in the beginner's guide.
one of these days i'm gonna get back on track w/ jdoom... maybe i hallucinated what i thought i read after all. i dunno; i guess stranger things have happened.
May 7th, 2002, 05:04 AM
I'm using jDoom 1.13 under WinXP and everything seems ok. (Only one problem that when talking about joystick initialization Doomsday fills console with crap characters - probably caused by non-english (russian, cp-1251) characters in joystick name)
May 7th, 2002, 05:43 AM
I've had no problems running it on XP Home.
May 8th, 2002, 07:15 PM
to the last coupla replies:
are you guys using kickstart, or KDX, to launch jDoom (or are you using .bat files)?
thanks for the responses!
May 9th, 2002, 11:06 PM
Both KickStart & .BAT works ok. Haven't used KDX (never tried)
May 10th, 2002, 07:32 PM
thanks. have you had any of the nasty slowdown i've read about here and on the email list (models/particles/etc.), and are you using the most recent version, 1.13.1?
May 28th, 2002, 04:20 AM
Using 1.13.1. MD2's are ok (no slowdowns, loading in 20 sec., then all ok). Really slows down with near rocket explosion if particles are enabled (seems like this is video card slowdown - Vanta 16Mb - 10fps when staying in particles cloud). Tested jDoom both under XP Pro & 98SE and under both is runs ok!
May 28th, 2002, 03:07 PM
June 2nd, 2002, 11:53 PM
for 3dfx and xp users..
iv got a voodoo3 2000/3000 , theres some drivers at voodoofiles.com - the only ones i could find that worked correctly are HOE 1.00 for xp pro..
during installation ,when asked if they'r xp certifide ,click continue anyway..
they work pretty good for 3rd party drivers , iv been using them for months now..
June 10th, 2002, 12:37 PM
Actually, I'm having some trouble! The words in the main menue are totally botched up. They're not appearing correctly... they're just big jumbly messes of red. I have NO IDEA how to fix it, but it sucks because I can't customize my controls or graphics settings, because I can't even read the menus! Very odd problem. NO IDEA why it doesn't work.
June 10th, 2002, 03:24 PM
darky, If you are using kickstart try this out.
In kickstart under the "graphics" tab see if texture compression is checked if it, uncheck it, hope that helps.
June 10th, 2002, 07:24 PM
What is kickstart?
I guess I'm not using it!
EDIT: OK, I can't even get Kicks.exe to start. I click it and I get:
Component 'COMDLG32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid
June 11th, 2002, 12:21 PM
works fine for me.
"Imp, a Cacodemon Story" the movie.
June 11th, 2002, 03:10 PM
this page may have what you need, darky.
namely the KickStart Full Install.
July 25th, 2002, 01:20 PM
I've tried the full install and the other suggestion, but my menus are still a load of grabled rubbish. I'm running WINXP Home, ATI Radeon 7500 graphics, OPENGL. Any suggestions?
July 28th, 2002, 08:49 AM
i cant get jDoom to work on xp, i start up kicks, tell it where the wads are, the hit play and it launches doomsday then hangs and gives me the error has occured message. i tried running in compatibility mode but it still didnt work. so then i downloaded the full kickstart thing. that didnt work. what am i doing wrong? btw i have a g4 4600 if that has to do with anything
i get this error when tryin Direct 3D....
Con_Init: Initializing the console.
Executable: Version 1.7.0 Jul 26 2002 (DGL).
Z_Init: Init zone memory allocation daemon.
32.0 Mb allocated for zone.
Parsing configuration files.
GL_Init: Initializing Doomsday Graphics Library.
DG_Init: Direct3D 8.1.
Direct3D: Call to CreateDevice failed:
DG_Init: Failed to initialize Direct3D.
July 28th, 2002, 01:24 PM
well, i JUST finally got around to upgrading doomsday myself [i started this thread a coupla months back], and the only problem i had was w/ kickstart. the full install fixed it, though. runs wonderfully, as long as i disable NAV auto-protect. i'm running winXP home on a p4 1.7, and a gf2 MX. btw, why aren't you rendering w/ openGL instead of d3d since you've got a gf4 4600?
July 28th, 2002, 02:41 PM
if i use opengl, it says doomsday has caused an error and has to close.
July 28th, 2002, 06:48 PM
that's weird. i'm no graphics guru, but i would think your card SHOULD be openGL-compliant. do you run any other games under openGL, or are they all d3d [besides anything using the unreal engine... as far as i know, it only uses d3d, or at least does so by default]? check in the "Bin" folder inside your doomsday directory and make sure you have the d3d and openGL .dll's in there. the drivers that came with the card should probably be new enough, but have you tried nvidia's detonator reference drivers? they were up to v29.42 last time i checked... as a last -ditch effort, you might wanna try just reinstalling everything-- the worst it could do is just replace your current files with the same ones, and add any that may be missing for whatever reason. it seems kinda unlikely that anything WOULD be missing, though.
vBulletin® v3.8.5, Copyright ©2000-2013, Jelsoft Enterprises Ltd.