First, to PAVROO,
Thank you for your very timely response. More details are in order. I am a registered user of VMWare and use it almost exclusively when using vm's to produce finished work in my charitable endeavors. I also have used Virtualbox for years but found that it manifests some really odd behavior from time to time with various combinations of distros, hardware, and configuration settings. So, I almost always use virtualbox ONLY when the use of it does not involve my serious finished work. I have enough issues without the chosen hypervisor giving me headaches when you least expect them. "Murphy's Law, right?"
As for the desktop vmware tools available to Sparky VMWare installs, I rarely install them because they add additional software and resource drain to a virtual machine setup intended to eventually serve an old pc system. Pavroo, as you suspected, I did not install the desktop tools when I created the iso file using Sparky-Backup-Sys. Should I have done so? If you say yes, then I will do so and try again.
As for my burning of the created iso file to usb thumb drives, I can tell you that I have done hundreds of transfers over the years with every available method at my disposal, my preference being using the dd command line options. Since Sparky's fabulous little tool "Live USB Creator" is just a convenient gui for the dd command, IT ROCKS! Don't get me wrong. I'm will always be a command line "kind of guy" but its one of the reasons I love Sparky distros so much. The small touches the developers and community incorporate into the desktop make working with Debian an absolute joy. For guys like me, 'IT'S A BOAT LOAD OF FUN!"
Sorry, I am rambling. Anyway Pavroo, any suggestion or ideas from you or your colleagues is welcome. The first rule of serious computing is never assume you know more than the next serious user. "Drain" them of as much knowledge as you can. I guarantee it will serve you well in the future.
NOW, this segment is directed to BLAZE. Through my years of field work and actual testing using Debian as a base, when working with older hardware, my research has yielded some revelations that will "debunk" many wive's tales concerning what is needed when working with older hardware. Everywhere there are discussions on the Internet, publications, working consordiums, educational institutions, etc., etc., is has always been discussed as a "matter of fact" that to succeed in re-purposing older equipment, you have to use Debian stable with old kernels. My work has proven this to be ABSOLUTELY FALSE. The determining factor is the old hardware's capabilities and nothing more. Eighty percent of the restored systems that I have put in use again are using Debian Testing. Does this surprise you? It did me. And I make these statements based on REAL EQUIPMENT running Debian Testing installations done by my own hand, not speculation or assumption made by others. The last nine pc's done by me are running Sparky distros with me using my "digital scalpel" to remove unnecessary services, software, scripts, and configurations.
Another advantage to using Debian Testing is more available firmware, multimedia, and software support. My work over the years has proven the Debian Stable is equivalent to another distro's SUPER STABLE. Debian Testing has proven to be equal to another distro's STABLE. Debian is that good and I know the Sparky fan base all know it.
Does this mean that I LOVE Debian only? Absolutely not. I LOVE ALL LINUX! I started using Linux in a serious way by starting with Red Hat 6.3, a long time before Fedora was even a thought of creation. It was so long ago that the video framework was XFREE86, not XORG as it is now. I also spent my early days with the business end of Suse 7 and 8 running the early versions of KDE, long before Novell purchased the company and even longer before OpenSUSE was a thought in anyone's mind. I still have the original packaging disks, manuals, everything. I have forgotten so much of what I learned in those early days.
I hope that my ramblings did not scare anyone away. I thought it was important to understand my frame of mind and reasons for certain decisions. I thank everyone for their support and willingness to help. I APPRECIATE YOU ALL. When I am finished with my current projects, I intend to provide all of my work and outlines for Sparky developers, community contributors, and sparky users to benefit Sparky distributions and their user base. I promise not to waste your time.
Always Grateful, Paul (sasdthoh)
ps: To PAVROO, check your private email account. I sent you some screenshots of my re-spin of Sparky that I am building for older systems. When it is finished, I guarantee it will BLOW YOU AWAY! You have my permission to share the screenshots with anyone that wishes to get a taste of what is coming.