Kumaki
Well-Known Member
It only works on Windows or Mac.
And THAT was my point. Because it could not run the software NATIVELY...and has the overhead of emulation...there is NO WAY...anyone could use a Pandy to wreak havoc on my software for my business...hence, there is no real security risk TO MY BUSINESS...issuing Pandy's to employees...especially seeing as how the software would not even be PUT on the Pandy to begin with.
Someone would have to first figure out how to get XP to run at a useable speed on a Pandy...and THEN...figure out how to get the software onto the Pandy...and even THEN, they still would need a password.
By the time they do all THAT....they would just use a full-powered compy if they wanted to wreak havoc...and not a Pandy.
The Pandy would be issued to employees, because I am having a database app made custom for me...which lists ICD9/ICD10 codes and CPT codes and Medicare Allowed Amounts for those CPT codes.
This way, any user would have this information on the fly. and THAT is the area in which the Pandy could be a use in my business...and thus could justify giving them to employees. didn't say I WOULD...but that this would be a justifyable business use.
And pointing out that, while some large companies might have issues with security that could be explouted with a Pandy...mine really doesn't, because of the simple fact that the software is not able to run on other than a Windows or Mac OS, and since the Pandy can't run new enough versions of these at useable speed...there really would not be any security risk above and beyond what I would already have...just having employees!
Because employees would have access to the software from a full-powered computer. SO...if THEY wanted to wreak havoc, why not just use the full-powered PC instead of dinking around with a Pandy trying to create problems?
And, assuming a stupid employee left their Pandy is a bus station somewhere...the software would never have been loaded onto the Pandy, anyway...and, even if iwere...and at useable speed, there is still a matter of a password...which I can change at a moment's notice.
My whole point being...issuing a Pandy to an employee...in my line of business, represents no more a security problem...than issuing them a signon and password.
COULD it be done? Maybe....and I really doubt it. But sure as hell not by a stranger that picked up an abandoned Pandy at the bus station. And the employee having a logon and password already represents a far more potential security risk...than them having a Pandy.
I mean...are you telling me I should not even HIRE someone who has a Pandy they bought themselves? Gimme a break!
So would it matter whether it was company-issued....or bought personally?
And THAT was my point. Because it could not run the software NATIVELY...and has the overhead of emulation...there is NO WAY...anyone could use a Pandy to wreak havoc on my software for my business...hence, there is no real security risk TO MY BUSINESS...issuing Pandy's to employees...especially seeing as how the software would not even be PUT on the Pandy to begin with.
Someone would have to first figure out how to get XP to run at a useable speed on a Pandy...and THEN...figure out how to get the software onto the Pandy...and even THEN, they still would need a password.
By the time they do all THAT....they would just use a full-powered compy if they wanted to wreak havoc...and not a Pandy.
The Pandy would be issued to employees, because I am having a database app made custom for me...which lists ICD9/ICD10 codes and CPT codes and Medicare Allowed Amounts for those CPT codes.
This way, any user would have this information on the fly. and THAT is the area in which the Pandy could be a use in my business...and thus could justify giving them to employees. didn't say I WOULD...but that this would be a justifyable business use.
And pointing out that, while some large companies might have issues with security that could be explouted with a Pandy...mine really doesn't, because of the simple fact that the software is not able to run on other than a Windows or Mac OS, and since the Pandy can't run new enough versions of these at useable speed...there really would not be any security risk above and beyond what I would already have...just having employees!
Because employees would have access to the software from a full-powered computer. SO...if THEY wanted to wreak havoc, why not just use the full-powered PC instead of dinking around with a Pandy trying to create problems?
And, assuming a stupid employee left their Pandy is a bus station somewhere...the software would never have been loaded onto the Pandy, anyway...and, even if iwere...and at useable speed, there is still a matter of a password...which I can change at a moment's notice.
My whole point being...issuing a Pandy to an employee...in my line of business, represents no more a security problem...than issuing them a signon and password.
COULD it be done? Maybe....and I really doubt it. But sure as hell not by a stranger that picked up an abandoned Pandy at the bus station. And the employee having a logon and password already represents a far more potential security risk...than them having a Pandy.
I mean...are you telling me I should not even HIRE someone who has a Pandy they bought themselves? Gimme a break!
So would it matter whether it was company-issued....or bought personally?