Hard Light Productions Forums

Off-Topic Discussion => General Discussion => Topic started by: Lynx on January 10, 2005, 03:16:18 pm

Title: Command&Conquer 1 in XP
Post by: Lynx on January 10, 2005, 03:16:18 pm

I've recently installed Tiberium conflict again on my XP machine but whenever I try to start it it says it can't find some procedureentering point or whatever in kernel32.dll and quits. Any help?

Title: Command&Conquer 1 in XP
Post by: Roanoke on January 10, 2005, 04:48:41 pm

You can have XP operate as per earlier versions (ME, 98 etc). It's in the XP help files.

Try that.

Title: Command&Conquer 1 in XP
Post by: Liberator on January 10, 2005, 04:55:00 pm

This  (http://www.planetcnc.com/features/techtroopers/classicsInXP/) should help.  It's a widespread problem and Westwood isn't around to help with the problem.

Title: Command&Conquer 1 in XP
Post by: Roanoke on January 10, 2005, 04:59:08 pm

Proven right. Once again. Thankyou, thankyou. ;)

Title: Command&Conquer 1 in XP
Post by: kode on January 10, 2005, 04:59:45 pm

dosbox...
http://dosbox.sourceforge.net/comp_list.php?showID=234&letter=C

Title: Command&Conquer 1 in XP
Post by: Liberator on January 10, 2005, 05:46:46 pm

I never could get dosbox to run MoM.

Title: Command&Conquer 1 in XP
Post by: Kosh on January 10, 2005, 07:54:01 pm

Westwood's coding practices suck, that is why their older games (C&C 1 and RA 1) have problems running on newer machines.

Title: Command&Conquer 1 in XP
Post by: Liberator on January 10, 2005, 11:04:39 pm

Well, since the original C&C(not Gold) required manual hardware configuation...

Title: Command&Conquer 1 in XP
Post by: Swamp_Thing on January 11, 2005, 12:50:09 am

Tiberian Sun works fine with my XP. I never needed to play in compatibility mode or anything. I just install and play...
Maybe it´s your system.

Title: Command&Conquer 1 in XP
Post by: Liberator on January 11, 2005, 01:08:33 am

I was talking about the original C&C, BEFORE the recode for Windows 95.  You had to manually configure your hardware.  Which meant you had to know what kind of sound card you had and whether it emulated a Soundblaster, what version of soundblaster(new or old), the IRQ it was set to, it's DMA address, and all that jazz.  You turkeys don't know how good you have it now having a unified standard like DX, it used to be a shot in the dark as to whether a game would work sometimes.

Title: Command&Conquer 1 in XP
Post by: kode on January 11, 2005, 07:03:07 am

that was the case with most, if not all, dos games. except for the ones using the pc speaker. and it was never a shot in the dark if you actually knew wtf you had in your comp. and usually it was irq 3, dma 5, and 220h, or something like that.

Title: Command&Conquer 1 in XP
Post by: Kosh on January 11, 2005, 09:57:00 pm

What I meant was they had problems running on NEWER machines. My brain was not entirely "there" when I wrote the post.

Title: Command&Conquer 1 in XP
Post by: Scuddie on January 12, 2005, 01:54:23 am

Quote

Originally posted by kode
and usually it was irq 3, dma 5, and 220h, or something like that.

**Cracks knuckles**

It was SET BLASTER=A220 I5 D1 H5 T6...
Breaking that down, was a 220-22F address, IRQ 5, DMA 1, High channel DMA 5, BLASTER type 6.  I believe that was the AWE32 IIRC.

I also remember the line for the original SB cards...  SET BLAST=A220 I7 D1, and NOTHING else worked.  Boy oh boy, those were the days :D.

Title: Command&Conquer 1 in XP
Post by: Flipside on January 12, 2005, 01:56:58 am

ROFL!

I try to forget them...