What screenshots of Windows do you have available?



2. Screenshots 41 through 50



The close program dialogue is shown (as from using control+alt+delete) with the resource levels in the top right corner showing 41% system resources and MSPaint in the background at 10x zoom.


Screenshot #41 - Whenever I work on an animation, I frequently have to put up with resource drainage. To explain what I mean by this, compare this screenshot with number 42 below. Note the resources at this moment. Also, I'm using 10x magnification in MSPaint, a secret magnification level that I accidentally found. To get 10x mag, just click on the magnifier and click way at the bottom of the 8x mark at the lowest line of pixels. It might be a bit tricky to do as that one pixel is tough to get around. It can be anywhere horizontally along that line but within the options display.



The close program dialogue is shown (as from using control+alt+delete) with the resource levels in the top right corner showing 14% system resources and MSPaint in the background showing one of the frames of an animation at 4x zoom.


Screenshot #42 - Compared to screenshot number 41 above, this is what happens after I work on the animation for about 30 minutes. All I was doing was copying from one MSPaint and pasting into the other (the one with the numbered file name) and opening files in the numbered MSPaint. Question is, why did I go from a semi-good 41% of my resources to a mere 14%? It's one of the glitches in Windows 98 SE.



The close program dialogue is shown (as from using control+alt+delete) with the resource levels in the top right corner showing 13% system resources and 20/20 in the background.


Screenshot #43 - Then, when I was saving all those bitmaps as a GIF image using 20/20, I ran into the same resource drainage troubles. In 20/20's case, all I was doing was opening the bitmap file, saving it as a GIF image with the same file name, opening the next bitmap image, saving it as a GIF image in the same way and so on. After about 100 times of opening the bitmaps and saving them as GIF, the resources crept dangerously low for no apparent reason. The funny thing is, when I close the program, and wait a few seconds, all of the resources used from the program are replenished. Not only that, but, after 100 more steps of doing it, I ran into the same problem. I only use 20/20 to save bitmaps as GIFs and PNGs. I don't use it as a drawing program, although it is one.



A notice is visible in the top left corner about no mouse detected and how to connect one shown with the desktop background loaded but without the icons and taskbar.


Screenshot #44 - From all of a sudden not responding any more, the mouse suddenly stopped responding and I was forced to use the keyboard to navigate between windows and programs. This shows an example of something that I almost never see, a notice saying that I don't have a mouse (even though it was connected into the PS/2 slot as it has been). As I had this notice, there really weren't any desktop shortcut icons nor the taskbar.



An error in Winamp tells that there was an error asking a thread to die.


Screenshot #45 - This is about the most unusual error I've ever encountered. I've never seen it before. However, previously, the GIMP wouldn't start up (it freezes at "loading script_fu" or whatever that is), 20/20 would error when I open a file saying of an access violation and I had 2 copies of the icon near the clock. I don't know what a thread is (except in the case of online forums, but this has nothing to do with the forums) so I can't explain that either. This error made me laugh when I first saw it so I immediately hit the Prt Scr key to snag a screenshot of it. Also, note the number of times some of my songs have played. This is common with me. I had an earlier screenshot showing of a more extreme case.



Pages: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Forward 10


Footnotes:
There are no footnotes for this page.