TechGrabage

Beta testing that is. I have been doing quite a bit of beta testing of late. Some pretty high profile stuff to. Tested a new inkjet printer from Dell and some cool stuff right now for Verizon. The best part are the incentives. For one of the most recent tests I received a DVD Recorder. Pretty cool. Hook it right up to the TV and record shows and movies directly to DVD. Only problem so far is my DirecTv receiver. The DVD Recorder can’t change the channel on the DTV receiver. I think I’ll hook up to the DirecTv TiVO receiver. This way I can transfer my hard drives recordings form the TiVO to DVD…

Kinda fun. I’d tell ya who I test for but that would decrease my chances for cool stuff!

-mwm

Users are objects in Active Directory. Shares via DFS can be objects in Active Directory. Printers are objects in Active Directory. There are so many objects in AD. Why do I need to create these convoluted scripts to attach printers and shares to users? Why? If they are all objects wouldn’t it make sense to be able assign printer objects to user objects as well as share objects to user objects? How about assigning a printer object to a group of user objects? This would make life a lot easier as far as administration of a Windows Domain goes…

Make sense right? Over simplified? Not possible?

-mwm

SUN… Of all companies. Perhaps it is the pinch SUN Microsystems has felt since the popularity of Linux and other open source initiatives picked up the steam they have of late that has made them be on the side of the user, not big business. SUN has created DReaM. An open source DRM methodology. DReaM is based on the user owning the license for purchased media for life. Current practice has DRM based on the DEVICE. Basing DRM on a device makes very little sense, for the user. When the device dies you lose all icenses for the media you have purchased, unless all your DRM license databases are backed up (are yours?).

Is there a good reason for not basing DRM on me instead of my devices?

-mwm