Monitor Tests Forum

Full Version: Custom Resolution Utility (CRU)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950
(10-31-2015 03:54 PM)francescobabbaro Wrote: [ -> ]Hi, I'm trying to solve the bug of GTA V about the refresh rate of 1080p locked at 59 hz.
I've tried to set only one detailed resolution (1920x1080p, both 60.000 hz and 59.94 hz, LCD standard) deleting all other resolutions, standard ones included. I've tried to set only one standard resolution (1920x1080p, 60 hz) deleting all other, detailed included. I've tried to set both standard and detailed resolutions setting as previous said, but nothing works. (Rebooted system after any change). Can you help me, please? I'm becoming crazy! Thanks a lot. (Sorry for my bad English).
(Amd video card, 15.10 beta drivers.).
AMD's driver automatically adds 59 Hz as an alias of 60 Hz for TV resolutions like 1920x1080. I haven't found a way around that, but that shouldn't matter because they're the same refresh rate.

If the game is stuttering at 59 Hz, then it's broken. Games aren't supposed to rely on the listed refresh rate to determine the frame rate, and vsync should automatically synchronize with the actual refresh rate.

Are you using vsync? If the game's vsync is causing stuttering, disable vsync in the game and enable it through the driver instead. CCC allows you to set options for individual games under Gaming > 3D Application Settings.
(11-03-2015 06:01 PM)ToastyX Wrote: [ -> ]
(10-31-2015 03:54 PM)francescobabbaro Wrote: [ -> ]Hi, I'm trying to solve the bug of GTA V about the refresh rate of 1080p locked at 59 hz.
I've tried to set only one detailed resolution (1920x1080p, both 60.000 hz and 59.94 hz, LCD standard) deleting all other resolutions, standard ones included. I've tried to set only one standard resolution (1920x1080p, 60 hz) deleting all other, detailed included. I've tried to set both standard and detailed resolutions setting as previous said, but nothing works. (Rebooted system after any change). Can you help me, please? I'm becoming crazy! Thanks a lot. (Sorry for my bad English).
(Amd video card, 15.10 beta drivers.).
AMD's driver automatically adds 59 Hz as an alias of 60 Hz for TV resolutions like 1920x1080. I haven't found a way around that, but that shouldn't matter because they're the same refresh rate.

If the game is stuttering at 59 Hz, then it's broken. Games aren't supposed to rely on the listed refresh rate to determine the frame rate, and vsync should automatically synchronize with the actual refresh rate.

Are you using vsync? If the game's vsync is causing stuttering, disable vsync in the game and enable it through the driver instead. CCC allows you to set options for individual games under Gaming > 3D Application Settings.

I don't think any game in windows 7 I've ever seen uses the AMD CCC setting for vsync. Maybe it works for games that don't have a vsync setting but I never got this to work in any game. In windows XP, the AMD CCC setting always applied.
(11-04-2015 12:15 AM)falkentyne Wrote: [ -> ]I don't think any game in windows 7 I've ever seen uses the AMD CCC setting for vsync. Maybe it works for games that don't have a vsync setting but I never got this to work in any game. In windows XP, the AMD CCC setting always applied.
Damn it. Why is everything broken? Maybe try RadeonPro instead.
Hey guys, i'm using a BenQ XL2430T with a dual-link DVI and was able to reach with manual timings:

1920x1080 @ 129Hz

Horizontal / Vertical
Front porch: 88 / 4
Sync width: 44 / 5
Total Pixels: 2165 / 1500
Sync Polarity: + / +

Refresh Rate: 193.50kHz / Pixel Clock: 418.93MHz

Should i use +/- for the polarity or there's no problem in keeping it +/+?

Checking by myself, i noticed that the automatic timings in the LCD - standard preset for 144Hz give a refresh rate of 166.610kHz, and if i change from 144 to 165.500Hz it goes up to 193.471kHz.. So what it means?
The monitor says it's at 129hz but it is working like a 165hz?

I'm new to the forum so i don't know how to post prints, but i have a link on imgur: http://imgur.com/bsP9P7Z

Windows 10 Pro, GTX 750 with driver 358.50. I've installed the patch for the driver in the past, but formated the computer many times after it, now i'm completely stock, with no mods to the original driver from nvidia.
Sorry for my bad english in case i made any mistake!
(11-04-2015 07:21 AM)Fidelity Wrote: [ -> ]Hey guys, i'm using a BenQ XL2430T with a dual-link DVI and was able to reach with manual timings:

1920x1080 @ 129Hz

Horizontal / Vertical
Front porch: 88 / 4
Sync width: 44 / 5
Total Pixels: 2165 / 1500
Sync Polarity: + / +

Refresh Rate: 193.50kHz / Pixel Clock: 418.93MHz

Should i use +/- for the polarity or there's no problem in keeping it +/+?

Checking by myself, i noticed that the automatic timings in the LCD - standard preset for 144Hz give a refresh rate of 166.610kHz, and if i change from 144 to 165.500Hz it goes up to 193.471kHz.. So what it means?
The monitor says it's at 129hz but it is working like a 165hz?

I'm new to the forum so i don't know how to post prints, but i have a link on imgur: http://imgur.com/bsP9P7Z

Windows 10 Pro, GTX 750 with driver 358.50. I've installed the patch for the driver in the past, but formated the computer many times after it, now i'm completely stock, with no mods to the original driver from nvidia.
Sorry for my bad english in case i made any mistake!

Hi,
You are using the wrong timings.
You are using the 60hz timings for 100-130hz; this must not be done.
These timings may or will cause image corruption because the scaler is being pushed too hard when you are using VT tweaks. Its fine without VT tweak but you can check "LCD standard" first to see your porch, sync and HT are too high.

For 100hz and higher, change 88/4 to 48/3 for front porch.
Change 44/5 to 32/5 for sync width
change horizontal total to 2080.
Vertical total is fine if you want to use VT tweak.

LCD reduced is for refresh rates higher than 129hz if you get black screen out of range error, you must use VT 1098 from 130 hz - 145 hz. You can not use "VT tweak" at 130hz+. Firmware will not allow it.

Toastyx can explain why 100hz/120hz don't use 88,4 and 44,5 and 2200 HT. If you check in CRU with "LCD standard" and enter 60hz you will see the timings. If you change 60hz to 100hz, you will see porch, sync and HT values change to lower.

This will also lower the pixel clock too. 125hz with VT 1500 should be around 396 MHz pixel clock with (48,3) front porch, and (32,5) sync width and (2080) HT.

Don't worry about polarity and don't change kHz manually. this is set by combination of other values.
(05-06-2015 01:27 AM)ToastyX Wrote: [ -> ]It adjusts the timing parameters to reduce the pixel clock when trying higher refresh rates. It's mostly useful for keeping 1920x1080 @ 72-77 Hz under 165 MHz, 1920x1080 @ 144 Hz under 330 MHz, and for reducing the pixel clock at 2560x1440 @ 100+ Hz with the Catleap/Tempest/QNIX/X-Star monitors.

It also uses CVT-RB for TV resolutions, but it won't do that at 3840x2160 @ 60 Hz because the pixel clock is so high. I might end up adding an "LCD native" option since the CEA timing parameters for TV resolutions are the same for 30/60/120 Hz, and then "LCD standard" can use CVT-RB for 3840x2160 @ 60 Hz without affecting the "LCD reduced" option.

Are you able to share the formula?
Quote:Hi,
You are using the wrong timings.
You are using the 60hz timings for 100-130hz; this must not be done.
These timings may or will cause image corruption because the scaler is being pushed too hard when you are using VT tweaks. Its fine without VT tweak but you can check "LCD standard" first to see your porch, sync and HT are too high.

For 100hz and higher, change 88/4 to 48/3 for front porch.
Change 44/5 to 32/5 for sync width
change horizontal total to 2080.
Vertical total is fine if you want to use VT tweak.

LCD reduced is for refresh rates higher than 129hz if you get black screen out of range error, you must use VT 1098 from 130 hz - 145 hz. You can not use "VT tweak" at 130hz+. Firmware will not allow it.

Toastyx can explain why 100hz/120hz don't use 88,4 and 44,5 and 2200 HT. If you check in CRU with "LCD standard" and enter 60hz you will see the timings. If you change 60hz to 100hz, you will see porch, sync and HT values change to lower.

This will also lower the pixel clock too. 125hz with VT 1500 should be around 396 MHz pixel clock with (48,3) front porch, and (32,5) sync width and (2080) HT.

Don't worry about polarity and don't change kHz manually. this is set by combination of other values.

Yeah, i didn't notice that my timings were according to the LCD Native preset. About the HT, does 2160 give me any benefit over 2080? Like a little reduction in blur, or something like the VT tweak? Changed the timings and it looks almost fine. Using 2080 HT i can see horizontal lines on the screen, if i up it to 2160 it goes away, that's why i set it that way, even with the correct timings they appear... Any problem to keep it at 2160? I only notice artifacts at 2175+ so i bumped down to 2160 for safety, but i don't actually know if it's safe or not, thanks for the help!
(11-05-2015 04:49 AM)Fidelity Wrote: [ -> ]
Quote:Hi,
You are using the wrong timings.
You are using the 60hz timings for 100-130hz; this must not be done.
These timings may or will cause image corruption because the scaler is being pushed too hard when you are using VT tweaks. Its fine without VT tweak but you can check "LCD standard" first to see your porch, sync and HT are too high.

For 100hz and higher, change 88/4 to 48/3 for front porch.
Change 44/5 to 32/5 for sync width
change horizontal total to 2080.
Vertical total is fine if you want to use VT tweak.

LCD reduced is for refresh rates higher than 129hz if you get black screen out of range error, you must use VT 1098 from 130 hz - 145 hz. You can not use "VT tweak" at 130hz+. Firmware will not allow it.

Toastyx can explain why 100hz/120hz don't use 88,4 and 44,5 and 2200 HT. If you check in CRU with "LCD standard" and enter 60hz you will see the timings. If you change 60hz to 100hz, you will see porch, sync and HT values change to lower.

This will also lower the pixel clock too. 125hz with VT 1500 should be around 396 MHz pixel clock with (48,3) front porch, and (32,5) sync width and (2080) HT.

Don't worry about polarity and don't change kHz manually. this is set by combination of other values.

Yeah, i didn't notice that my timings were according to the LCD Native preset. About the HT, does 2160 give me any benefit over 2080? Like a little reduction in blur, or something like the VT tweak? Changed the timings and it looks almost fine. Using 2080 HT i can see horizontal lines on the screen, if i up it to 2160 it goes away, that's why i set it that way, even with the correct timings they appear... Any problem to keep it at 2160? I only notice artifacts at 2175+ so i bumped down to 2160 for safety, but i don't actually know if it's safe or not, thanks for the help!

Increasing the HT has NO benefit whatsoever except putting extra pressure on the scaler. I'm not sure if it will affect certain Vertical totals causing frameskipping or not; if you want I can test that for you. Usually if a certain vertical total causes frameskipping (you can see it EASILY with blur reduction on, in Test UFO->Alien invasion....if you see the image "jump" repeatedly or every several seconds its frameskipping), then try another VT in the range of 1497-1502.

I'm not sure if HT affects that or not. However raising the HT does raise the pixel clock so its not certain what's causing what. NO effect on blur reduction.
Usually there's no 'danger' as far as I know....if it has artifacts then its too high. But usually you should keep the HT at default, and lower it if you want a lower pixel clock.

The only thing that makes the "overdrive" better is by turning on blur reduction first and then setting "AMA" to high AFTER enabling blur reduction. On XL2411Z and XL2420Z (and MAYBE XL2430T, u can test for urself ok?), it lowers the overdrive inverse ghosting by about 10%. On XL2720Z, it lowers it by a drastic 50% (much better), but you have to drop the contrast lower to avoid too much normal ghosting.

*edit* ok changing HT does NOT affect frameskipping is a certain VT frameskips (e.g. VT 1502 at 85hz refresh rate, VT 1501 is perfect on XL2720Z).
Quote:Increasing the HT has NO benefit whatsoever except putting extra pressure on the scaler. I'm not sure if it will affect certain Vertical totals causing frameskipping or not; if you want I can test that for you. Usually if a certain vertical total causes frameskipping (you can see it EASILY with blur reduction on, in Test UFO->Alien invasion....if you see the image "jump" repeatedly or every several seconds its frameskipping), then try another VT in the range of 1497-1502.

I'm not sure if HT affects that or not. However raising the HT does raise the pixel clock so its not certain what's causing what. NO effect on blur reduction.
Usually there's no 'danger' as far as I know....if it has artifacts then its too high. But usually you should keep the HT at default, and lower it if you want a lower pixel clock.

The only thing that makes the "overdrive" better is by turning on blur reduction first and then setting "AMA" to high AFTER enabling blur reduction. On XL2411Z and XL2420Z (and MAYBE XL2430T, u can test for urself ok?), it lowers the overdrive inverse ghosting by about 10%. On XL2720Z, it lowers it by a drastic 50% (much better), but you have to drop the contrast lower to avoid too much normal ghosting.

*edit* ok changing HT does NOT affect frameskipping is a certain VT frameskips (e.g. VT 1502 at 85hz refresh rate, VT 1501 is perfect on XL2720Z).

I did that test and didn't notice any frameskipping, it's all smooth. I don't really know how to explain this, at VT 1502 and with blur reduction ON, the image looks so clear that you can actually see the individual pixels and the lines they are in, i play CS:GO and it's easy to notice when you look at a smoke grenade or looking at a piece of skin in movies, i think it's related to the pixel clock, because when it goes down it seems to disappear, but the brightness also goes down so i'm not really sure. *thinking about it, it looks like when you go near the tv and see all the pixels crammed in there* I sit at 3 to 4 inches from the screen and it's clearly visible when watching movies or playing CS. More ↑↑↑ HT, Less ↓↓↓ effect. My settings on the monitor:

Blur reduction(ON) - Strobe Duty: 15 (Max is 25/ 0~25)
Strobe Phase: 0 (I can reach 49 before the monitor blacks out)
Black eQualizer: 0
Color Vibrance: 9
Low Blue Light: 0
Instant Mode: On
Auto game mode: Off
-----------------------------
Picture Mode: Standard
Brightness: 100
Contrast: 52
Sharpness: 5
Gamma: 5
Color temp: R:98 / G:100 / B:99
AMA: High

Like i said, using 2080 i notice it very easily and the more i go up in the HT the less i can see. If you know anything about it, let me know! Thanks for all the help!
(11-06-2015 06:55 AM)Fidelity Wrote: [ -> ]
Quote:Increasing the HT has NO benefit whatsoever except putting extra pressure on the scaler. I'm not sure if it will affect certain Vertical totals causing frameskipping or not; if you want I can test that for you. Usually if a certain vertical total causes frameskipping (you can see it EASILY with blur reduction on, in Test UFO->Alien invasion....if you see the image "jump" repeatedly or every several seconds its frameskipping), then try another VT in the range of 1497-1502.

I'm not sure if HT affects that or not. However raising the HT does raise the pixel clock so its not certain what's causing what. NO effect on blur reduction.
Usually there's no 'danger' as far as I know....if it has artifacts then its too high. But usually you should keep the HT at default, and lower it if you want a lower pixel clock.

The only thing that makes the "overdrive" better is by turning on blur reduction first and then setting "AMA" to high AFTER enabling blur reduction. On XL2411Z and XL2420Z (and MAYBE XL2430T, u can test for urself ok?), it lowers the overdrive inverse ghosting by about 10%. On XL2720Z, it lowers it by a drastic 50% (much better), but you have to drop the contrast lower to avoid too much normal ghosting.

*edit* ok changing HT does NOT affect frameskipping is a certain VT frameskips (e.g. VT 1502 at 85hz refresh rate, VT 1501 is perfect on XL2720Z).

I did that test and didn't notice any frameskipping, it's all smooth. I don't really know how to explain this, at VT 1502 and with blur reduction ON, the image looks so clear that you can actually see the individual pixels and the lines they are in, i play CS:GO and it's easy to notice when you look at a smoke grenade or looking at a piece of skin in movies, i think it's related to the pixel clock, because when it goes down it seems to disappear, but the brightness also goes down so i'm not really sure. *thinking about it, it looks like when you go near the tv and see all the pixels crammed in there* I sit at 3 to 4 inches from the screen and it's clearly visible when watching movies or playing CS. More ↑↑↑ HT, Less ↓↓↓ effect. My settings on the monitor:

Blur reduction(ON) - Strobe Duty: 15 (Max is 25/ 0~25)
Strobe Phase: 0 (I can reach 49 before the monitor blacks out)
Black eQualizer: 0
Color Vibrance: 9
Low Blue Light: 0
Instant Mode: On
Auto game mode: Off
-----------------------------
Picture Mode: Standard
Brightness: 100
Contrast: 52
Sharpness: 5
Gamma: 5
Color temp: R:98 / G:100 / B:99
AMA: High

Like i said, using 2080 i notice it very easily and the more i go up in the HT the less i can see. If you know anything about it, let me know! Thanks for all the help!

Hi,
You sort of contradicted yourself in your last post. First you said "the higher the pixel clock, the more "pixels" you can see on the screen (is this true?).

Then you said "More HT, less effect". I don't understand what this means. This sounds like you just said the exact opposite of what I wrote in the above sentence.

When you use the VT tweak, look on windows at a GREY background. Aida64 has a grey background image on its monitor test but the free version has an annoying watermark. You can try using the GREEN test on Eizomonitor test.....

http://www.eizo.be/support/monitortest.html

When you increase the HT do you notice a scanlines type effect on the all green background in the eizo test? Is this what you are describing?

Are you saying you LIKE having a high HT over a 2080 HT, with a VT 1502??

I never noticed any sort of...um....."seeing pixels clearer" like you said. I only know that if the pixel clock gets too high, you get image corruption (shimmering/flickering pixels).

is *THIS* the effect you are seeing?
[Image: Xtmd1Yu.jpg]

(this is 125hz, VT 1497, pixel clock 389.22 (displayport).
you can see a scanlines effect. Notice every few horizontal rows, a line of pixels is brighter than the ones around it?)

Here is 120hz (120.5hz actually, default VT (1144)).
Notice everything looks more even and any scanlines effect of alternating lighter pixel rows is almost completely gone?

[Image: HD69EUj.jpg]
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950
Reference URL's