Skip to main content

Developing RSS feed in Screensaver With C# Express Edition 2005



Alrite ladies follow these steps to make your own screen saver. Whether you'll do it or not do it following my advice is NOT my concern. I'll set it occasionally for the heck of it for myself.

Here is a screen shot of having done it all and setting and validating my feed on the Screen Saver that we just cooked.



For whole set of print screens on setting up and running it then see it on my foto gallery here.
Steps are simple...
  • download the C#Express 2005 from MSDN
  • Start a project (as shown in the print screen)
  • Build it
  • Save it
  • Go to the folder where it was saved
  • Check under /bin and find the *.scr file
  • Copy that file to your windows\system32 dir (if in XP)
  • Select the NEWS screen saver
  • Edit settings and image(s) of your choice
  • And Run it
simple ain't it!

And play this AVI file to see how it works.

PS: As you can see it was a *Ready Baked code*, no development but you might want to...
o Do a mouse roll over to open a particular news directly from the screen saver, and we'll see how we can do that!

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...