euankirkhope

www.nvidia.com or reactorcritical.com when it's leaked.

MJy ati rage pro AGP 2x (xpert 98) was slow when I bought it, about the same as my voodoo1 (maybe less) but it was good at 2D, and high res, low detailed games (forsaken)... Thats why I bought a TNT 2 years ago, time to start saving money I'm afraid

There are also lots of reasonably simple causes... Take the card out and check that the soldered joints on the VGA socket are all 100% stuck down, and that there are no dry joints. Also check the cables on both monitors. Do you use a VGA extension cable/splitter? if so remove it... Try the monitor in another PC. The ramdac should know what a good and insane signal is, perhaps trying the original shipped drivers (too ensure a 100% hardware match) if it blows again, you know who to sue. Using beta software drivers (except shipped beta software ) would invalid your warranty so never mention what driver version you were using. Just say "what do mean driver version? I just installed off cdrom, like the instructions said..."

I said Win98 doesn't use SMP, because the system is dual boot (is it?) although there is only 1 processor (was the PC previosly a SMP system, with new mobo?). Thus I deduct that the Q3a folder will be shared between the systems. It may therefore be configured for w2k, but in win98 some extra options may slow the system, by for example copying the folder from the other SMP system. Win98 may handle the multithreaded modes much less poorer. It could be possible. Maybe install a clean version for win98?

no problems here ------------------ System Spec: FIC VA-503+ 1.1b bios JE438 CPU Current Limiter Disabled AMD K6-2 550 (300 when I talk to FIC tech support) 128Mb SSi PC100 STB Velocity 4400 16Mb PAL TV-Out Hauppauge Wintv Realtek 8029 LAN Creative ES1371 (PCI64v) 56.6K (AkA 44k) ISA Modem Creative 48mx CDROM Memorex TriMaxx200(DVD/CDR/CDRW, 6,4,24) Maxtor 91301U3 13Gb LS120 and com and lpt i/o conflict error during bios startup. Hardware fault caused by win2k beta3 and dodgy bios, now irrepairable.

runs beos nice! ------------------ System Spec: FIC VA-503+ 1.1b bios JE438 CPU Current Limiter Disabled AMD K6-2 550 (300 when I talk to FIC tech support) 128Mb SSi PC100 STB Velocity 4400 16Mb PAL TV-Out Hauppauge Wintv Realtek 8029 LAN Creative ES1371 (PCI64v) 56.6K (AkA 44k) ISA Modem Creative 48mx CDROM Memorex TriMaxx200(DVD/CDR/CDRW, 6,4,24) Maxtor 91301U3 13Gb LS120 and com and lpt i/o conflict error during bios startup. Hardware fault caused by win2k beta3 and dodgy bios, now irrepairable.

Win98 dosen't use SMP. Also the texture and mipmap settings maybe different in the display panel for win98... run dxdiag and see what it says, is AGP working. Turn off that seti@home! CPU cache setting may be wrong, or win98 has stopped using it due to a change, or is in some way not utilising it to its full capacity. (maybe a re-install needed?, I've thrown in lots of different CPUs in my PC, but the change from K6-2 to K6-2CXT core in win98 didn't go down to well, but NT4 didn't notice, W2K beta didn't work at the time ) [This message has been edited by euankirkhope (edited 13 June 2000).]

just copy the files, and also when you goto run the game change the shortcut (or click on) the file to the other exe (i can't remember the name, i thinks its grim.exe) instead of the usual long named file) Also if it complains about registry stuff, or its not installed copy the stuff below to a txt file, and rename it to a .reg file. Take care not to name it like grim.reg.txt! then double click on it. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\LucasArts Entertainment Company LLC] [HKEY_LOCAL_MACHINE\SOFTWARE\LucasArts Entertainment Company LLC\Grim Fandango] [HKEY_LOCAL_MACHINE\SOFTWARE\LucasArts Entertainment Company LLC\Grim Fandango\v1.0] "Executable"="d:\\games\\Grim\\GrimFandango.EXE" "Install Path"="d:\\games\\Grim" "Source Path"="E:" "CD Path"="E:" "Analyze Path"="E:\\INSTALL\\DXDIAG.exe" "Source Dir"="E:\\" "GrimDataDir"="E:\\GRIMDATA" "InstallType"=dword:00000009 "Version"="1.0" "ExperimentalDisplay"=hex:01,00,00,00 "Last3DDevice"=hex:e0,3d,e6,84,aa,46,cf,11,81,6f,00,00,c0,20,15,6e "LastDisplayDevice"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 "GrimMannyState"="suit" "Magic"=dword:00092774 "MovementMode"="Character"

FPS in what? Roughly speaking, if you look at all the hyped up reviews with insane 800Mhz CPUs then I would consider the 2 options... 1 at the low resolutions you should get somewhere between half and the same as what an insane machine gets... 2 at the higher resolutions (AKA insane resolutions, most people can't even dream of) you would probably see a much greater performance drop. This said I'm sure it would be arse spankingly fast

Yeah, My tnt1 does it often although the latest drivers are very good, now its mostly just my CPU overheating and something causing fastfat.sys to hang the system now and again, all and all its very good. Apparantly the IRQ not less or equal happens when a driver/program tries to access memory outwith its allocated regions. IE MS blame the hardware companies ------------------ System Spec: FIC VA-503+ 1.1b bios JE438 CPU Current Limiter Disabled AMD K6-2 550 (300 when I talk to FIC tech support) 128Mb SSi PC100 STB Velocity 4400 16Mb PAL TV-Out Hauppauge Wintv Realtek 8029 LAN Creative ES1371 (PCI64v) 56.6K (AkA 44k) ISA Modem Creative 48mx CDROM Memorex TriMaxx200(DVD/CDR/CDRW, 6,4,24) Maxtor 91301U3 13Gb LS120 and com and lpt i/o conflict error during bios startup. Hardware fault caused by win2k beta3 and dodgy bios, now irrepairable.

Its just a driver fault, usually by a hardware "intensive" devices, most likely it happens when your hard tasking the video card. The IRQ not less or equal is a kernel error, and I suppose means the computer didn't get the results it expected, which are derived from the drivers... But in retrospect windows probably just picks a random number and tells you thats the error that occured

yeah thats why i said that i set my pc to us with a uk keyboard (and UK time). (did I say that)... If you have local set to UK and you type "? naked women" you only have the option of lycos and a few other cruddy UK search engines. Press customise to see... With a US local you can pick practically any, and have direct access by typing ? in the address bar, thats the point I was making

I've always found that playing games on NT was much better than win98!

DX8 on the system stated below is perfect boobman: ------------------ System Spec: FIC VA-503+ 1.1b bios JE438 CPU Current Limiter Disabled AMD K6-2 550 (300 when I talk to FIC tech support) 128Mb SSi PC100 STB Velocity 4400 16Mb PAL TV-Out Hauppauge Wintv Realtek 8029 LAN Creative ES1371 (PCI64v) 56.6K (AkA 44k) ISA Modem Creative 48mx CDROM Memorex TriMaxx200(DVD/CDR/CDRW, 6,4,24) Maxtor 91301U3 13Gb LS120 and com and lpt i/o conflict error during bios startup. Hardware fault caused by win2k beta3 and dodgy bios, now irrepairable.

When u gona learn that computers aren't supposed to work with win2k, and it was only invented to keep the tech support industry busy? We all know what system u've got cos u've almost posted about the shi$"$" problems that w2k spews up as many time as me! With the last driver release for my TNT, AGP miraculously became enabled, but is has made no difference to the speed of any games (no doubt its being faked!). You have a mobo to die for, unlike my via 503+, (didn't you have a via?) that shouldn't have any probs. Most likely the G400 drivers are too imature (my tnt drivers have just matured ) so give a while yet... As for the memory, it shouldn't matter as, if we take the speed of the memory (or latency) for each clock cycle; if (and only if) one dimm is too slow to keep up and supply the correct data by the next clock cycle will an error occur. If this is the case then you are overclocking the memory and thats just silly. So you won't be doing that will you Just sit back, and wait. Your time will come. Ps. thanks for the bios updates! Update! My TNT doesn't work no matter what unless I'm in ACPI mode, although the com ports don't work its worth it, so give it a try. At the last resort you can use a serial I/O board like me. [This message has been edited by euankirkhope (edited 11 June 2000).]

nice website! and domain name... i'm stuck with euan.iscool.net but its cack anyhow. Does overlay work on you wintv, and what setup/model if yes.

Send me your Mobo details and I'll sort out your serial port problems. At the moment I have ACPI enabled, but my com ports don't work. TO get round this I have my PS2 mouse connected to the PS2 mouse port on my mobo (need proper cable, and mobo pins that doesn't fake it, and connect to a serial port). My yamaha Midi ports are connected via an old serial I/O port on its com1, its LTP1 is used for my playstation dual shock in win98. The mobo's com ports are disabled in the bios setup, and the LPT port (set to LPT2) is uses for the printer. This way everything is at least functional. If you tried setting the PC to "standard PC" it should have fixed everything, did it? If it didn't you need to delete the com port from device manager, and redetect it after a reboot, and/or add new hardware.

Best bets is that there is something called acpi installed in your PC. Its a type of hardware management that is supposed to be more efficient, but with some motherboards (mostly socket 7) it doesn't quite work right. For now you can try this (with no need for a mouse): press windows+break hold ctrl and press tab until you get to hardware press alt+D press tab to highlight you computer name then press down to go to Ports (com + lpt) press right then select the port you mouse is connected to, press enter. If the Device status windows says something is wrong, and states that it assumes the device is not a com port, or mentions "latch", or data being wrong, then continue... (if its says there is a resource confict then skip the rest) tab to cancel, press enter press up to go to Computer Then enter it by going right then down. If it says "Advanced configuration blah blah blah"... Press enter (if not skip the rest) Ctrl+tab to get to driver Press Alt+P (update driver) Press enter press alt+D (display a list...) Enter (pc goes hunting) tab to show... and select "show all..." Tab back to models and select "Standard PC" Press enter and follow the instructions (i'm not going any further, cos it'll waste alot of my time undoing it ) Windows should be restarted after up[censored] the driver. If your mouse starts working then you have either a non-conformat bios (get updated one from manufacture website that states ACPI compatibilty, or stay as it in standard PC mode) If you have a resource conflict then restart the PC and press "del" at the power on bios screen (power on self test). Goto you peripheral setup and see what the com ports are set to. There shouldn't be anything wrong here, as you probably had the mouse working fine in win9x or whatever you may have had before. If neither the above are correct then maybe it is a video card driver problem, but that is less likely, and would go away if you start up in safe mode. You might want to print that out (if your printer works or your at another computer). Have fun [This message has been edited by euankirkhope (edited 10 June 2000).]

My setups a bit boring: receive radio waves, fed into 75ohm antenna socket, and thats it. Tuning in Pal-I mode. On the audio front, I don't use the line out, instead I soldered on 4 pins (i didn;t have the heart to butcher an old soundcard for one of those (MPC-3?) connectors that CD-Roms use) direct on to line out. The card actually has the copper tracks for a cd pass through, but I didn't bother adding it on, I just took the output only. The biggest source of noise seems to always be the CDROM audio out. This way I don't have to exit the PC, and I can connect directly to the internal AUX connector next to the cdrom connector on my soundblaster PCI64v (es1371). Now I know you'll say something like try the line-out connector, but both my custom connector and the line out are on the same bits of wire, so it makes no difference. I have also checked it many times when I get no audio, just out of paranoia. After going through the soundcard its fed out (when thers is actually a signal) to a cheap Philips dolby pro-logic amp (with a separate cheap Pioneer amp for the rear speakers). Good for star-trek. With beos I've tried every outout and input for the soundcard, and tuner. It seams to be something to do with the MUX number, and decode format being "odd". I'll try the drivers again, as I've just backed up to a clean re-install, due to huge number of BSOD's, fastfat, kmode, etc, and memory not read or written errors. Found out that the case fan had become disconnected. Duh. And seti@home didn't help either.

Well... maybe seti@home + mysteriously dead case fan, could be the cause of the probs! I've re-installed and it seams fine. (for now). So thats what the burning smell was... I though is was something to do with the cd writer...that cup of water sure cooled it down... its really really quiet now...

Damm no luck But thanks lots Tried them both, the first installed the drivers, but the tvapp refused to run, some obsure filtercap() function errror. Tried the hauppauge TV app, but it refused to run with out the hauppauge drivers. driver no2 was more sucessful, but was very slow in initiating button clicks and changing settings, and also never displayed any picture what so ever. It did however make the pop sounds that the hauppauge drivers make Basically neither worked although its probably due to the customisation of the drivers for each specific card. I think I need the drivers without any apps supplied, that way there will be no preset customisations. The second set of drivers had configuration settings for both the TNT and VIA chipsets, also overlay works, although there was no picture. Also Hauppauge were kind enough to add in a MSP34xx (04) sound processor for NICAM stereo, which messes up the sound demod, the BT878A had sound built in. Basically I have a BT878, a philips tuner and a MSP3404 sound chip. Any ideas? Are there any normal tv (non manufacturer type) apps that will work with the generic drivers? Likewise there's no sound in beos, but it works in linux.

The region checker is there to make sure your not using a US cd outside the US, for rather feeble reasons, and also for keyboard mapping, and possibly to find the fastest network server. All you do is change the region setting in the control panel. As I keep my PC set to US language but with a UK Keyboard. That way internet explorer allows me to use altavista as the direct default instead of some cruddy localised search engine like www.lycos.co.uk

Just for the record, Children: The only difference between DX7 and DX7a is that DX7 had a very minor error with the function assignment in some USB joysicks that was found by a N64 emulator IN WINDOWS 98. So if the Win2000 version of DX7 doesn't have this error what does that mean? Also if the two operating systems are very much different, and the binaries are incompatible between OS's them why would the revision numbers mean anything with respect to the other OS? With repect to D3d DDraw and what not there the exact same between dx7 and dx7a. The only chage is in Dinput, which is in its self very minor.

NT4 is the best. None of this "lets have DX7 and ACPI" It pure hardware simplicity. PnP is even a no no unless you install afterwards from directly from the CDROM. Plays all the Quakes blissfully, Ah sigh the good ol' days. If its questionable it wouldn't work in NT4 fullstop. That way it really was stable. Win2k is still a bit unfinished however. Take my machine for instance I keep on getting stupid errors like: The protected system file c:\winnt\system32\ksinterf.ax could not be verified as valid because Windows File Protection is terminating. Use the SFC utility to verify the integrity of the file at a later time. Or, this ones extremely common: The instruction at "0x00231803" referenced memory at "0x00000000". The memory could not be "read". Like so: The device, \Device\Ide\IdePort0, did not respond within the timeout period. Don't know what this is but it certainly fills up the event log: Unable to read the disk performance information from the system. Disk performance counters must be enabled for at least one physical disk or logical volume in order for these counters to appear. Disk performance counters can be enabled by using the Hardware Device Manager property pages. Status code returned is data DWORD 0. Not to mention hourly fastfat.sys, and Kmode exception bsod's ammongst many other interesting ones. The last one (10 mins ago) was something about driver_power_status being unknown? Looks like its time for a re-install. But will it be NT4 or NT5?

The AGP slot and PCI slot 1 are physically connected to the same IRQ line. So if either slot has a hungry device the other slot must be left empty.