Jump to content
Sign in to follow this  
Clavius

MDS Specifications?

Recommended Posts

F6 doesn't change anything that would make anything work, it just turns on some extra logging that I need in certain situations. As for why it didn't work the first time... no idea, it's your pc, not mine ;)

 

Yes the pdhAddCounter errors are why you don't get any graphs. Either your install of windows is messed up or something has renamed/changed/taken over those counters.

 

Open up perfmon.msc and see what counters you have available to you.

 

If I right click one of the 3 visible in the main screen and hit properties, this is the screen i get:

 

perfmon.png

Share this post


Link to post
Share on other sites
As for why it didn't work the first time... no idea, it's your pc, not mine ;)

I'm reasonably sure that I changed nothing between the two burns. (Besides pressing F6)

 

If I right click one of the 3 visible in the main screen and hit properties, this is the screen i get:

First of all, thank you very much for your time!!!

 

I did as you said and got only the second of your three entries.

Actually, I got another PerfNet-Error immediately after opening perfmon.msc.

I tried to add the other two entries, but could not find them in the list.

After a little googleing I think it might be because I've disabled file and printer sharing due to paranoid security reasons. (I read that disabling it causes the server-service to disappear)

So I guess I have to live without CPU- and Buffer-graphs!?

(Buffer-graphs would be nice though!)

 

Clavius

Share this post


Link to post
Share on other sites

Something odd must have just happened the first time and the MD5 calculation code either never got started for the 'device' buffer or it gave an error part way through - which would then disable it. It's impossible to say what caused it without catching it in the act of failing.

Feel free to keep logging the extra debug stuff (when you remember) until it happens again (if it happens again). Then let me see the log and maybe between us we can work out why it's happening.

 

 

Now back to the performance counters...

 

So if you try to add a counter, do not get 'Processor' in the 'Performance Object' drop down list? (or anything like it?)

 

I find it odd that simply disabling file + print sharing would have such an impact on performance counters!

Share this post


Link to post
Share on other sites
Feel free to keep logging the extra debug stuff (when you remember) until it happens again (if it happens again). Then let me see the log and maybe between us we can work out why it's happening.

Sounds good to me! :)

 

So if you try to add a counter, do not get 'Processor' in the 'Performance Object' drop down list? (or anything like it?)

Exactly! :(

Share this post


Link to post
Share on other sites

Hmm how weird! There must be some counter there somewhere that can monitor cpu usage or task manager wouldn't work in that respect!

Share this post


Link to post
Share on other sites

Very weird, because task manager is working OK on my system.

Unfortunately I have no knowledge about this performance monitor stuff, but ever since ImgBurn is capable of recording the CPU-usage, I get PerfNet error 2004 in eventviewer. And at eventid.net and in google-groups they say this error appears if the server service is not running, which may occur when disabling file and printer sharing.

Don't know if this is really related, but to me it seems so.

 

When maybe some time far in the future I will have more time, I will do some more research.

 

Thank you anyway!

Share this post


Link to post
Share on other sites

lol of course it might just be easier to enable the server service and do a test burn?!

 

If you've got a firewall, you don't really need to worry about file and print sharing anyway.

 

Most people have 2 levels of security, The 1st in their router (+ NAT), and then a 2nd on the actual pc.

Share this post


Link to post
Share on other sites

No router here!

Just one PC directly connected to the DSL-Modem!

(Software-Firewall of course (Kerio))

 

I know that I'm a bit paranoid, but I think I would rather live without the two graphs than enabling f+p sharing when I don't really need f+p sharing.

OK, I could do it temporarily for one test-burn without connecting to the Internet during the test, but I'm to anxious that I mess something up.

 

Write-speed and Verify-speed graphs are working, which is most important to me.

Share this post


Link to post
Share on other sites

News from my MD5-issue:

 

Something odd must have just happened the first time and the MD5 calculation code either never got started for the 'device' buffer or it gave an error part way through - which would then disable it. It's impossible to say what caused it without catching it in the act of failing.

Feel free to keep logging the extra debug stuff (when you remember) until it happens again (if it happens again). Then let me see the log and maybe between us we can work out why it's happening.

It happened again! :(

And I'm afraid, there is no extra debug-message related to this! :mellow:

(Only the PdhAddCounter-stuff, which we discussed in the previous posts)

 

 

I 20:29:53 ImgBurn Version 2.1.0.0 started!

I 20:29:53 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

W 20:29:53 Drive D:\ (FAT32) does not support single files > 4 GB

W 20:29:53 Drive E:\ (FAT32) does not support single files > 4 GB

I 20:29:54 Initialising SPTI...

I 20:29:54 Searching for SCSI / ATAPI devices...

I 20:29:54 Found 1 CD-RW, 1 DVD-ROM and 1 DVD?RW!

W 20:30:10 Program 'Debug Mode' has been Enabled!

I 20:30:14 Operation Started!

I 20:30:14 Source File: G:\TEST3.MDS

I 20:30:14 Source File Sectors: 2.140.328 (MODE1/2048)

I 20:30:14 Source File Size: 4.383.391.744 bytes

I 20:30:14 Source File Volume Identifier: TEST3

I 20:30:14 Source File Implementation Identifier: Daikin U.S. Comtec Lab

I 20:30:14 Source File File System(s): ISO9660; UDF (1,02)

I 20:30:14 Destination Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

I 20:30:14 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 4x; 6x; 8x)

I 20:30:14 Destination Media Sectors: 2.295.104

I 20:30:14 Write Mode: DVD

I 20:30:14 Write Type: DAO

I 20:30:14 Write Speed: 2,4x

I 20:30:14 Link Size: Auto

I 20:30:14 Test Mode: No

I 20:30:14 BURN-Proof: Enabled

D 20:30:25 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

D 20:30:25 Device Buffer Size: 6.291.456 bytes.

D 20:30:25 Device Buffer Available: 6.291.456 bytes.

I 20:30:25 Filling Buffer...

I 20:30:25 Writing LeadIn...

I 20:30:48 Writing Image...

I 20:43:57 Synchronising Cache...

I 20:44:01 Closing Track...

I 20:44:02 Finalising Disc...

I 20:44:18 Image MD5: dd94dd55c1ecf054be129275368f7454

I 20:44:19 Exporting Graph Data...

I 20:44:19 Graph Data File: G:\TEST3_PLEXTOR_DVDR_PX-716A_1.10_RITEK-R03-02_2,4x.ibg

I 20:44:19 Export Successfully Completed!

I 20:44:19 Operation Successfully Completed! - Duration: 00:14:03

I 20:44:19 Average Write Rate: 5.425 KB/s (3.9x) - Maximum Write Rate: 6.695 KB/s (4.8x)

I 20:44:19 Cycling Tray before Verify...

I 20:44:45 Device Ready!

I 20:44:47 Operation Started!

I 20:44:47 Source Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

I 20:44:47 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: RITEK-R03-02) (Speeds: 4x; 6x; 8x)

I 20:44:47 Image File: G:\TEST3.MDS

I 20:44:47 Image File Sectors: 2.140.328 (MODE1/2048)

I 20:44:47 Image File Size: 4.383.391.744 bytes

I 20:44:47 Image File Volume Identifier: TEST3

I 20:44:47 Image File Implementation Identifier: Daikin U.S. Comtec Lab

I 20:44:47 Image File File System(s): ISO9660; UDF (1,02)

D 20:44:48 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

I 20:44:48 Verifying Sectors...

I 20:51:05 Image MD5: dd94dd55c1ecf054be129275368f7454

I 20:51:05 Exporting Graph Data...

I 20:51:05 Graph Data File: G:\TEST3_PLEXTOR_DVDR_PX-716A_1.10_RITEK-R03-02_2,4x.ibg

I 20:51:05 Export Successfully Completed!

I 20:51:05 Operation Successfully Completed! - Duration: 00:06:18

I 20:51:05 Average Verify Rate: 11.354 KB/s (8.2x) - Maximum Verify Rate: 16.278 KB/s (11.8x)

I 20:52:15 Close Request Acknowledged

I 20:52:15 Closing Down...

I 20:52:15 Shutting down SPTI...

I 20:52:15 ImgBurn closed!

Share this post


Link to post
Share on other sites

Hmm ok, maybe it's not failing then!

 

I've just gone over the code again and have tweaked some of the API calls after having a bit of a re-think on how to interpret them!

 

Basically I think one of them was returning 0 for the length of the hash and so it was never really calculated and put into string format - which would then be displayed in the log.

 

Sorry but you'll just have to wait until v2.2.0.0 gets released and then test that one. (No date planned as yet)

Share this post


Link to post
Share on other sites
Sorry but you'll just have to wait until v2.2.0.0 gets released and then test that one. (No date planned as yet)

Actually I'm very glad that you haven't just discarded this issue! :)

 

(I guess I can't convince you to let me try out a beta-version? :rolleyes: )

Share this post


Link to post
Share on other sites

lol I only ever discard non existent things!

 

I can see with my own eyes that *something* isn't working properly on your PC and I actually quite like the challenge of finding out what that is :)

 

I've not even given the beta team a beta version since the final v2.1 release..... far too much testing for me to do first! Maybe once I give them a beta I'll PM you or something.

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.