pollst and pollog - INFO

CATALYST maker · May 16, 2003, 03:21 PM

A couple of you are asking about two new files that appear on your root C drive. (pollst.txt and pollog.txt)

I asked around and turns out that someone here inadvertantly left a DEBUG statement on inside of driver.

The files are deleted each time the system is booted up, and then will grow with DEBUG statements until the next reboot. The size should not be that big unless you never reboot. You can safely delete these two files from your C: root drive. They are not dangerous to your system in any way.

This is some of the stuff we have to do when we build drivers and do testing on them. Kinda cool huh?

I have been assured this will not appear in future releases.

SciDoctor · May 16, 2003, 03:38 PM

Might they be handy if people are having problems that will show up in these files

euan · May 16, 2003, 03:43 PM

Might as well help out then eh...

-15:43:43:609-0x00000650...Calling StartServiceCtrlDispatcher()
-15:43:43:625-0x00000654...Entering CNTService::ServiceMain()
-15:43:43:625-0x00000654...Entering CNTService::Initialize()
-15:43:43:625-0x00000654...CNTService::SetStatus(1333056, 2)
-15:43:43:625-0x00000654...CNTService::SetStatus(1333056, 4)
-15:43:43:625-0x00000654...Leaving CNTService::Initialize()
-16:13:14:718-0x000005a4...Calling StartServiceCtrlDispatcher()
-16:13:14:734-0x000005ac...Entering CNTService::ServiceMain()
-16:13:14:734-0x000005ac...Entering CNTService::Initialize()
-16:13:14:734-0x000005ac...CNTService::SetStatus(1332984, 2)
-16:13:14:734-0x000005ac...CNTService::SetStatus(1332984, 4)
-16:13:14:734-0x000005ac...Leaving CNTService::Initialize()
-16:23:09:359-0x00000590...Calling StartServiceCtrlDispatcher()
-16:23:09:359-0x00000594...Entering CNTService::ServiceMain()
-16:23:09:359-0x00000594...Entering CNTService::Initialize()
-16:23:09:359-0x00000594...CNTService::SetStatus(1332984, 2)
-16:23:09:359-0x00000594...CNTService::SetStatus(1332984, 4)
-16:23:09:359-0x00000594...Leaving CNTService::Initialize()
-17:02:54:890-0x000005c0...Calling StartServiceCtrlDispatcher()
-17:02:54:921-0x000005cc...Entering CNTService::ServiceMain()
-17:02:54:921-0x000005cc...Entering CNTService::Initialize()
-17:02:54:921-0x000005cc...CNTService::SetStatus(1332984, 2)
-17:02:54:921-0x000005cc...CNTService::SetStatus(1332984, 4)
-17:02:54:921-0x000005cc...Leaving CNTService::Initialize()
-17:35:29:625-0x00000600...Calling StartServiceCtrlDispatcher()
-17:35:29:625-0x00000604...Entering CNTService::ServiceMain()
-17:35:29:625-0x00000604...Entering CNTService::Initialize()
-17:35:29:625-0x00000604...CNTService::SetStatus(1333056, 2)
-17:35:29:625-0x00000604...CNTService::SetStatus(1333056, 4)
-17:35:29:625-0x00000604...Leaving CNTService::Initialize()
-17:47:19:640-0x00000594...Calling StartServiceCtrlDispatcher()
-17:47:19:640-0x00000598...Entering CNTService::ServiceMain()
-17:47:19:640-0x00000598...Entering CNTService::Initialize()
-17:47:19:640-0x00000598...CNTService::SetStatus(1332984, 2)
-17:47:19:640-0x00000598...CNTService::SetStatus(1332984, 4)
-17:47:19:640-0x00000598...Leaving CNTService::Initialize()
-18:01:43:843-0x00000570...Calling StartServiceCtrlDispatcher()
-18:01:43:843-0x00000574...Entering CNTService::ServiceMain()
-18:01:43:843-0x00000574...Entering CNTService::Initialize()
-18:01:43:843-0x00000574...CNTService::SetStatus(1332984, 2)
-18:01:43:843-0x00000574...CNTService::SetStatus(1332984, 4)
-18:01:43:843-0x00000574...Leaving CNTService::Initialize()
-18:14:03:984-0x0000059c...Calling StartServiceCtrlDispatcher()
-18:14:03:984-0x000005a0...Entering CNTService::ServiceMain()
-18:14:03:984-0x000005a0...Entering CNTService::Initialize()
-18:14:03:984-0x000005a0...CNTService::SetStatus(1332984, 2)
-18:14:03:984-0x000005a0...CNTService::SetStatus(1332984, 4)
-18:14:03:984-0x000005a0...Leaving CNTService::Initialize()

lol!

Lets hope we don't have log entries being written during games. The fanatics will have a fit.

Dark_Apocalypse · May 20, 2003, 05:18 PM

Quote:

Originally posted by euan
Might as well help out then eh...

lol!

Lets hope we don't have log entries being written during games. The fanatics will have a fit.

thats an understatement... they'll go nuclear... i would too if an over looked thing like that caused me to get killed in a fragging match...

Azariel · May 20, 2003, 09:27 PM

Thanks for the reply CM.

CATALYST maker · May 20, 2003, 11:05 PM

Quote:

Originally posted by Dark_Apocalypse
thats an understatement... they'll go nuclear... i would too if an over looked thing like that caused me to get killed in a fragging match...

dont worry these logs dont impact performance and dont go logging while you are gaming. They only activate during log on routines

Okio · May 25, 2003, 07:43 AM

has anyone tried write-protecting the files?

Vegie · May 25, 2003, 09:37 AM

ahh well spose they forgot to take it out

whats it used for (more detail) if u wouldnt mind.

BMG_Cya=- · May 25, 2003, 10:56 AM

I was wondering what the hell-o that was.
Thought it was my anti-vrus or firewall programs doing
something weird. Didn't take the time to read 'em.

They are very annoying. What files do you need to delete
to get rid of these, and keep them from coming back?

macstorm · May 26, 2003, 12:51 PM

I guess there's no way to stop them from loading as Ravey said this files will not appear in future releases...
Have a good CNTService day!

jaz00k · May 26, 2003, 05:59 PM

Well there's no way of deleting these files permanently as they just regenerate next time you reboot. However, if you don't like the fact they're on view just give them read-only and hidden properties, although I'm not sure how this will impact the debug process if at all...

Alpha · May 26, 2003, 06:13 PM

You could disable the ATI Hotkey Poller service if you don't intend to use hotkeys.
This will prevent the log files from being made.

Okio · May 27, 2003, 01:22 AM

create a folder with the same name as the file(s)?

May 16, 2003, 03:21 PM	#1	Advertisement (Guests Only) Login or Register to remove this ad
CATALYST maker dominATIon Join Date: Oct 2002 Location: ATI Canada Posts: 1,671	pollst and pollog - INFO A couple of you are asking about two new files that appear on your root C drive. (pollst.txt and pollog.txt) I asked around and turns out that someone here inadvertantly left a DEBUG statement on inside of driver. The files are deleted each time the system is booted up, and then will grow with DEBUG statements until the next reboot. The size should not be that big unless you never reboot. You can safely delete these two files from your C: root drive. They are not dangerous to your system in any way. This is some of the stuff we have to do when we build drivers and do testing on them. Kinda cool huh? I have been assured this will not appear in future releases. __________________ Follow me on Twitter for exclusive Catalyst updates http://twitter.com/CatalystMaker

May 16, 2003, 03:38 PM	#2
SciDoctor Rage3D Veteran Join Date: Nov 2000 Location: Location: ENGLAND Posts: 2,499	Might they be handy if people are having problems that will show up in these files __________________ ...an ounce of perception , a pound of obscure....

May 16, 2003, 03:43 PM	#3
euan Rage3D Veteran Join Date: Jul 2000 Location: Glenrothes, UK / Luenen, Germany Posts: 7,099	Might as well help out then eh... -15:43:43:609-0x00000650...Calling StartServiceCtrlDispatcher() -15:43:43:625-0x00000654...Entering CNTService::ServiceMain() -15:43:43:625-0x00000654...Entering CNTService::Initialize() -15:43:43:625-0x00000654...CNTService::SetStatus(1333056, 2) -15:43:43:625-0x00000654...CNTService::SetStatus(1333056, 4) -15:43:43:625-0x00000654...Leaving CNTService::Initialize() -16:13:14:718-0x000005a4...Calling StartServiceCtrlDispatcher() -16:13:14:734-0x000005ac...Entering CNTService::ServiceMain() -16:13:14:734-0x000005ac...Entering CNTService::Initialize() -16:13:14:734-0x000005ac...CNTService::SetStatus(1332984, 2) -16:13:14:734-0x000005ac...CNTService::SetStatus(1332984, 4) -16:13:14:734-0x000005ac...Leaving CNTService::Initialize() -16:23:09:359-0x00000590...Calling StartServiceCtrlDispatcher() -16:23:09:359-0x00000594...Entering CNTService::ServiceMain() -16:23:09:359-0x00000594...Entering CNTService::Initialize() -16:23:09:359-0x00000594...CNTService::SetStatus(1332984, 2) -16:23:09:359-0x00000594...CNTService::SetStatus(1332984, 4) -16:23:09:359-0x00000594...Leaving CNTService::Initialize() -17:02:54:890-0x000005c0...Calling StartServiceCtrlDispatcher() -17:02:54:921-0x000005cc...Entering CNTService::ServiceMain() -17:02:54:921-0x000005cc...Entering CNTService::Initialize() -17:02:54:921-0x000005cc...CNTService::SetStatus(1332984, 2) -17:02:54:921-0x000005cc...CNTService::SetStatus(1332984, 4) -17:02:54:921-0x000005cc...Leaving CNTService::Initialize() -17:35:29:625-0x00000600...Calling StartServiceCtrlDispatcher() -17:35:29:625-0x00000604...Entering CNTService::ServiceMain() -17:35:29:625-0x00000604...Entering CNTService::Initialize() -17:35:29:625-0x00000604...CNTService::SetStatus(1333056, 2) -17:35:29:625-0x00000604...CNTService::SetStatus(1333056, 4) -17:35:29:625-0x00000604...Leaving CNTService::Initialize() -17:47:19:640-0x00000594...Calling StartServiceCtrlDispatcher() -17:47:19:640-0x00000598...Entering CNTService::ServiceMain() -17:47:19:640-0x00000598...Entering CNTService::Initialize() -17:47:19:640-0x00000598...CNTService::SetStatus(1332984, 2) -17:47:19:640-0x00000598...CNTService::SetStatus(1332984, 4) -17:47:19:640-0x00000598...Leaving CNTService::Initialize() -18:01:43:843-0x00000570...Calling StartServiceCtrlDispatcher() -18:01:43:843-0x00000574...Entering CNTService::ServiceMain() -18:01:43:843-0x00000574...Entering CNTService::Initialize() -18:01:43:843-0x00000574...CNTService::SetStatus(1332984, 2) -18:01:43:843-0x00000574...CNTService::SetStatus(1332984, 4) -18:01:43:843-0x00000574...Leaving CNTService::Initialize() -18:14:03:984-0x0000059c...Calling StartServiceCtrlDispatcher() -18:14:03:984-0x000005a0...Entering CNTService::ServiceMain() -18:14:03:984-0x000005a0...Entering CNTService::Initialize() -18:14:03:984-0x000005a0...CNTService::SetStatus(1332984, 2) -18:14:03:984-0x000005a0...CNTService::SetStatus(1332984, 4) -18:14:03:984-0x000005a0...Leaving CNTService::Initialize() lol! Lets hope we don't have log entries being written during games. The fanatics will have a fit. __________________ sys® Start Folding for Team Rage3D. Just enter as settings username "EuanK" Team number "64". :evil: "Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd all run around in a darkened room munching pills and listening to repetitive music...." -- - Kristian Wilson, CEO, Nintendo Gaming Corporation, Inc, 1989 Last edited by euan : May 16, 2003 at 03:49 PM.

May 25, 2003, 07:43 AM	#7
Okio leh ar~ cheap jing! Join Date: Nov 2002 Location: Peoples Republic of China Posts: 1,462	has anyone tried write-protecting the files? __________________ .

May 25, 2003, 09:37 AM	#8
Vegie we all like to be on top. Join Date: Apr 2003 Location: Brisbane Posts: 695	ahh well spose they forgot to take it out whats it used for (more detail) if u wouldnt mind. __________________ ¤ Intel i7 920 @ 3.6 ¤ Gigabyte GA-EX58-UD5 ¤ Corsair TR3X6G1600C8D ¤ 2x SLI GIGABYTE X260 896MB ¤ WD RAPTOR 150GIG ¤ WIN 7 X64 ¤ Logitech Z5500 5.1 ¤ BENQ 24" V2400W ¤ CORSAIR HX1000 ¤ LIAN LI PC-X2000 ¤

May 20, 2003, 09:27 PM	#5
Azariel Radeon HD 5770 Join Date: Apr 2003 Location: Australia Posts: 211	Thanks for the reply CM.

May 25, 2003, 10:56 AM	#9
BMG_Cya=- Radeon HD 5750 Join Date: Feb 2003 Location: United States Posts: 131	I was wondering what the hell-o that was. Thought it was my anti-vrus or firewall programs doing something weird. Didn't take the time to read 'em. They are very annoying. What files do you need to delete to get rid of these, and keep them from coming back? __________________ Athlon XP 2800+ (Barton 2184/356) [color=sky blue]Gigabyte Radeon 9800 Pro (128)[/color] Sapphire Radeon 9700 Pro (Atlantis) 512/256 MB Ultra Gold 2700 Dual Channel DDR(O'clocked)[color=royal blue]WD/Seagate/Maxtor 80,60,40 GB HDD's [/color] [color=sea-green] MSI K7NG2-ILSR Ultra MOBO[/color] Klipsch 5.1's with 400-watt sub-woofer...Omega Drivers Audigy Gamer X[color=dark red] Kingwin 450-watt 3-fan PSU[/color] - Microsoft Dual-Optical Mouse...MS K/B...and alot of stuff I'm forgetting atm... 3DMark03 score (6045) 3DMark03

May 26, 2003, 12:51 PM	#10
macstorm Newbie Join Date: May 2003 Location: Sahara (very cold here!) Posts: 1	I guess there's no way to stop them from loading as Ravey said this files will not appear in future releases... Have a good CNTService day!

May 26, 2003, 05:59 PM	#11
jaz00k Radeon HD 5570 Join Date: Sep 2002 Location: right here, right now Posts: 49	Well there's no way of deleting these files permanently as they just regenerate next time you reboot. However, if you don't like the fact they're on view just give them read-only and hidden properties, although I'm not sure how this will impact the debug process if at all...

jaz00k's System Specs
Motherboard	ASUS A8V
CPU	AMD Athlon64 4000+ @ 2.64GHz
Graphics	ATI Radeon X1900Pro AGP
Memory	2GB OCZ EL DDR
Display	Samsung 913N
Soundcard & Speakers	Audigy 2ZS

May 26, 2003, 06:13 PM	#12
Alpha Tastes like chicken Join Date: Sep 2000 Location: Toronto Posts: 5,139	You could disable the ATI Hotkey Poller service if you don't intend to use hotkeys. This will prevent the log files from being made. __________________ RIP Vengeance :(

May 27, 2003, 01:22 AM	#13
Okio leh ar~ cheap jing! Join Date: Nov 2002 Location: Peoples Republic of China Posts: 1,462	create a folder with the same name as the file(s)? __________________ .

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode