Printing, XMS, online, licensing & online future
Sept 10, 2018 2:50:11 GMT 1
Post by johnswolter on Sept 10, 2018 2:50:11 GMT 1
I'm going to be using vDOS to run a single user Clipper program on a single computer that produces ASC-II text & control codes. I don't believe the program uses characters beyond the 1st 128 ASC-II characters, to 0x7E. It's printing to a HP 4000 series LaserJet set to accept PCL input. That should work according to the vDOS documentation.
2nd, can the XMS be expanded beyond the 10 MBytes configured into vDOS. The configuration documentation suggested that parameter is not available in the current version. I'm not sure as of now if more than 10 MByte would be needed.
3nd, Based on reading the FAQ & other documentation, it's not clear if printing is included in the base distribution. Additionally the "nag screen" discussion suggests that registration is required at a cost of 35 euros to have that removed & printing enabled. The customer is stating the printing aspect of vDOS is important to any sales decision. Let me know how you handle this issue if printing is not available in the base distribution.
4th, I'm installing Windows 10 Pro or equivalent license on this machine for a eight person small business. There is a small network for five computers, mostly laptops used outside their office. No network Windows Server with Domain Controller and or Active Directory roles exists today. Combining M$ AZURE's or use of M$'s free download D-C & or A-D for very small company could complicate the licensing. Soon even two computers may act like a managed network.
4.5-ish, Amazon Web Services has Windows 10 Pro instances that have a default "Simple" Active Directory role even if a single Windows 10 instance is activated. These online options appear to complicate your license policy. AWS & Azure are now running all these instances as VMs or as Containerized dedicated OSs running applications. I can't see how your simple licensing policy, as nice as it is, can't suffer some growing pains.
As of now the online instance market is wide open. M$- or IBM PC DOS instances are not available from an online service. The only way to run a DOS program is to obtain a LINUX or Windows instance online & modify it to run those programs. vDos may solve that problem for Windows online at Azure or AWS.
Approaching this issue with a LINUX instance requires running a machine emulator inside the instance within which DOS could be executed. Some confusion exists about running a VM program like VM VirutalBox because it's a VM itself. If VirtualBox can run inside Windows or LINUX desktops then DOS can be loaded into that virtual pc.
Considering your current state of knowledge about vDOS, I could image it would be a less than challenging for you to devise a useful online product. I hope you might self-educate yourselves about online issues & solve this problem.
Cheers,
John S Wolter
Wolter Works, LLC
2nd, can the XMS be expanded beyond the 10 MBytes configured into vDOS. The configuration documentation suggested that parameter is not available in the current version. I'm not sure as of now if more than 10 MByte would be needed.
3nd, Based on reading the FAQ & other documentation, it's not clear if printing is included in the base distribution. Additionally the "nag screen" discussion suggests that registration is required at a cost of 35 euros to have that removed & printing enabled. The customer is stating the printing aspect of vDOS is important to any sales decision. Let me know how you handle this issue if printing is not available in the base distribution.
4th, I'm installing Windows 10 Pro or equivalent license on this machine for a eight person small business. There is a small network for five computers, mostly laptops used outside their office. No network Windows Server with Domain Controller and or Active Directory roles exists today. Combining M$ AZURE's or use of M$'s free download D-C & or A-D for very small company could complicate the licensing. Soon even two computers may act like a managed network.
4.5-ish, Amazon Web Services has Windows 10 Pro instances that have a default "Simple" Active Directory role even if a single Windows 10 instance is activated. These online options appear to complicate your license policy. AWS & Azure are now running all these instances as VMs or as Containerized dedicated OSs running applications. I can't see how your simple licensing policy, as nice as it is, can't suffer some growing pains.
As of now the online instance market is wide open. M$- or IBM PC DOS instances are not available from an online service. The only way to run a DOS program is to obtain a LINUX or Windows instance online & modify it to run those programs. vDos may solve that problem for Windows online at Azure or AWS.
Approaching this issue with a LINUX instance requires running a machine emulator inside the instance within which DOS could be executed. Some confusion exists about running a VM program like VM VirutalBox because it's a VM itself. If VirtualBox can run inside Windows or LINUX desktops then DOS can be loaded into that virtual pc.
Considering your current state of knowledge about vDOS, I could image it would be a less than challenging for you to devise a useful online product. I hope you might self-educate yourselves about online issues & solve this problem.
Cheers,
John S Wolter
Wolter Works, LLC