

SilentBob
Members-
Posts
105 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by SilentBob
-
"the type of file system is NTFS. cannot lock current drive. chkdsk cannot run because the nolume is in use by another process. would you like to schedule this volume to be checked the next time the system restarts? (Y/N)" ??? SB
-
OK I made a dskchk and "windows found problems with the file system" now - how do I enable the "F" option? what line do I need to write? cause when I typed : chkdsk/F it thought I mean volume F which is the second drive on my computer. what line exectly do I have to type after: c:\documents and settings\Elan>? SB
-
bump again SB
-
OK Rzero, 1. I think that the Drwtsn log will not help us very much. I think it doesn't have any relation to my problen cause it's dated 3/6/2006. I can give you m,y last LockOn error log from the LockOn directory: DXProceduralTexture: failed to create, D3DERR_INVALIDCALL. Dispatcher: track version = 512091930 Dispatcher: initial random seed = 890578 Dispatcher: apply random seed = 890578 Cosmos: Mission date assigned - Year:2004, Month:6, Day:22 2. I checked my device meneger and all is fine except "Atitray" (?) wich has a yellow "!" next to it. 3. and do you think a windows reinstall can help? thanx SB
-
bump
-
Tried the Omega drivers - no joy there :mad: SB
-
Rzero- first, I want to thank you for your help and good will, I appreciate it alot. 1. Drwatsn does let me view the log file - but I don't know where to look in it for the error. 2. I will try the omega drivers and let you know if there's any change - I doubt it. 3. soundcard - realtek AC97 audio 4, will a complete reinstall of windows do the trick? I start to think of some desparate actions such as reformatting....:( SB
-
bump
-
watson 32 gave me this: C:\windows\system32\dwwin.exe 80000003 ntdll!DbgBreakPoin(7C951230) can you understand something of it? SB
-
Thanks RZero mu HD is 180GB in size with alot of free space, I have another HD with 180GB but I use it for other stuff - not games. my VM is on 2048MB min/max. I'd sure like to know exectly how to trace the problem - could u be more specific about it? the lnks you gave are good but they are talking about another problem - it's also ralated to 0X00000040 (like I know what it is!:mad: ) but it's not about memory failing to be "read/write" SB
-
*sigh* it's gone from bad to worse. now I can't even launch a mission. I CTD after I hit "FLY" button. WHAT AM I DOING WRONG??????????? SB
-
I haven't find anything helpfull in Google either. could it be something to do with virtual memory? swap files? maybe it has something to do with registry entries? I am at a loss here... SB
-
thanx Neodark I'm waiting SB
-
I have tried other video drivers (6.1, 6.2, 6.3, 6.4) and I use 1200X1600 res. I use to get it with 1024X1280 and 1024X768. I don't think it's vid card related though - I don't have this prob with other "heavy" games as Doom3, HL2 or COD2. SB
-
neodark - all I get is this messege on my desktop: "The instruction at "0x01a93db0" referenced memory at "0x00000004". The memory could not be "read". or: The instruction at "0x77bcb9b5" referenced memory at "0x00030006". The memory could not be "write". no blue screen or something like that. Paralyzer: Version of FC is D/L SB
-
well I did the memtest and everything seems to be OK with my sticks...could it be related to Norton Antivirus? a friend of mine told me that he had an error like me and uninstalling Norton solved it... could it be? SB
-
what version do I need to D/L? SB
-
Thanx Ice, but I have other games that are very Memory emanding as DOOM 3, COD2, F4, Need for speed MW and others and I don't have any problem with them. should I steel check the sticks? SB
-
Hi all, I am experiencing a lot of CTD's with my new rig. (specs at the sig section below) the CTD's are random, they happen in mid flight or when I press "quit" to exit a mission but they happen almost every time I play. first I get a black screen with the sound still playing at the background than after a nimute or so, than I CTD and I get an error message: The instruction at "XXXXX" referenced memory at "xxxxx". The memory could not be "read". sometimes I get a black screen with the sound still playing but after a nimute or so I slowly return to the game - first I see the terrain then the HUD symbology outlines, then the cockpit appears and game continues....with no error message at all... I tried reinstalling a couple of times but the problem continued... what should I do? I am playing FC 1.12a SB
-
Confirmed: adaptive AA is better with 6.4 on my X1800XL BUT since LockOn doesn't like that feature (CTD's and all) it's quite pointless. anyways, I'll stick with this Cat 6.4. it's a good driver after all. SB
-
endeed, no need for more than 2XFSAA when in 12X16 res. but as AF goes, I found out that AFX4 costs me about 10 FPS in A-10 missions close to the ground, and not so much in F-15 missions high in the sky. I got "Adaptive Anti Aliasing" too, whatever that means... SB
-
I use 1280X1024 4XAA (all other settings are maxed of course except water on medium and Vis range on medium) but I leave the AF to "let the app descide" I does AF actually does? is the difference really noticable? SB
-
Hi gents. As I have a Radeon X1800XL card I have the option of a feature called "Temporal Anti Aliasing" its supposed to "double the effective anti aliasing image quality level by alternating the sample pattern every other frame" I don't know if Ati had this feature in earlier cards, but LockOn seems to dislike this feature. whenevr I turn this feature on I get the "black screen - now reboot" especially in heavy action (like high speed close dogfighting with 4-5 A/C in the air) when I turn it off my system can handle it no problem (with the occasional CTD here and there) this thing happens only with LockOn. other games take this Temporal antialiasing without any problem. any one else got this problem? SB
-
meaning? SB
-
The reason I don't use the internal FPS counter is because it's almost nreadable for me. the numbers flash and change in irratic manner between 19-85 with no apparent reason.I don't know whats the reason for it, it didn't act like that on my older rig (P4 2.6, radeon9700Pro 128 MB). So I have to use a more "stable" FPS counter. SB