Giving up in trying to replace XP

I've spent weeks trying to get various aspects of Windows 10-32-bit to play
nicely with all my Windows programs, including 16-bit and a samba-based LAN.

One of them would work if run under cmd,exe but it needed command line
arguments and I could not find a way to run the combination from a batch
file run from a shortcut.

Under XP it has to 'talk' to a 32-bit exe program through which it
conditions text before sending it to the printers. That program executes
properly under Windows 10 but the 16-bit program can no longer find it.

Other often used 16-bit programs produce error messages that make no sense.
It is not worth replacing them as the set-up costs would outweigh the
benefit.

Luckily my 7-year old 4-core AMD processor with 8GB of RAM has adequate
power to handle Mageia Linux hosting VMware and two virtual machines: XP and
Windows 10 and that is where I will stay.

Having run numerous operating systems side by side, The sheer bloat
insularity of the latest incarnation leaves me convinced that Microsoft has
developed a death wish. It's a tragedy but so many large firms sometimes
forget who their customers are and paid the price.

Mind you, Kodak are making solutions for a public wanting prints again, so
....


--
Mageia 5 for x86_64, Kernel:4.4.16-desktop-1.mga5
KDE version 4.14.5 on an AMD Phenom II X4 Black edition.

pinnerite wrote:
I've spent weeks trying to get various aspects of Windows 10-32-bit to play
nicely with all my Windows programs, including 16-bit and a samba-based LAN.

One of them would work if run under cmd,exe but it needed command line
arguments and I could not find a way to run the combination from a batch
file run from a shortcut.

Under XP it has to 'talk' to a 32-bit exe program through which it
conditions text before sending it to the printers. That program executes
properly under Windows 10 but the 16-bit program can no longer find it.

Other often used 16-bit programs produce error messages that make no sense.
It is not worth replacing them as the set-up costs would outweigh the
benefit.

Luckily my 7-year old 4-core AMD processor with 8GB of RAM has adequate
power to handle Mageia Linux hosting VMware and two virtual machines: XP and
Windows 10 and that is where I will stay.

Having run numerous operating systems side by side, The sheer bloat
insularity of the latest incarnation leaves me convinced that Microsoft has
developed a death wish. It's a tragedy but so many large firms sometimes
forget who their customers are and paid the price.

Mind you, Kodak are making solutions for a public wanting prints again, so
...

Did you use the Compatibility tab on the 16-bit programs ?

Paul

Paul wrote:

pinnerite wrote:
I've spent weeks trying to get various aspects of Windows 10-32-bit to
play nicely with all my Windows programs, including 16-bit and a
samba-based LAN.

One of them would work if run under cmd,exe but it needed command line
arguments and I could not find a way to run the combination from a batch
file run from a shortcut.

Under XP it has to 'talk' to a 32-bit exe program through which it
conditions text before sending it to the printers. That program executes
properly under Windows 10 but the 16-bit program can no longer find it.

Other often used 16-bit programs produce error messages that make no
sense. It is not worth replacing them as the set-up costs would outweigh
the benefit.

Luckily my 7-year old 4-core AMD processor with 8GB of RAM has adequate
power to handle Mageia Linux hosting VMware and two virtual machines: XP
and Windows 10 and that is where I will stay.

Having run numerous operating systems side by side, The sheer bloat
insularity of the latest incarnation leaves me convinced that Microsoft
has developed a death wish. It's a tragedy but so many large firms
sometimes forget who their customers are and paid the price.

Mind you, Kodak are making solutions for a public wanting prints again,
so ...

Did you use the Compatibility tab on the 16-bit programs ?

Paul

I used every published trick in the book, including two compatibility modes.
I would have expected cmd.exe to accept .bat files, which might have cracked
it but ...


--
Mageia 5 for x86_64, Kernel:4.4.16-desktop-1.mga5
KDE version 4.14.5 on an AMD Phenom II X4 Black edition.

On 01/10/2016 21:48, pinnerite wrote:
I've spent weeks trying to get various aspects of Windows 10-32-bit to play
nicely with all my Windows programs, including 16-bit and a samba-based LAN.

*I don't want to read your crap but let me tell you one thing: Windows
10 is not meant for Idiots so don't waste your time on it. Leave it to
us to enjoy it. *




--

If you want to filter all of my posts then please read this article:
https://support.mozilla.org/en-US/kb/organize-your-messages-using-filters
In step 7 select "Delete"

With over 350 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Good Guy wrote:

On 01/10/2016 21:48, pinnerite wrote:
I've spent weeks trying to get various aspects of Windows 10-32-bit to
play nicely with all my Windows programs, including 16-bit and a
samba-based LAN.

*I don't want to read your crap but let me tell you one thing: Windows
10 is not meant for Idiots so don't waste your time on it. Leave it to
us to enjoy it. *


Well, that seems to eliminate the only ones left.






--
Mageia 5 for x86_64, Kernel:4.4.16-desktop-1.mga5
KDE version 4.14.5 on an AMD Phenom II X4 Black edition.

pinnerite wrote:

Paul wrote:

pinnerite wrote:
I've spent weeks trying to get various aspects of Windows 10-32-bit to
play nicely with all my Windows programs, including 16-bit and a
samba-based LAN.

One of them would work if run under cmd,exe but it needed command line
arguments and I could not find a way to run the combination from a batch
file run from a shortcut.

Under XP it has to 'talk' to a 32-bit exe program through which it
conditions text before sending it to the printers. That program executes
properly under Windows 10 but the 16-bit program can no longer find it.

Other often used 16-bit programs produce error messages that make no
sense. It is not worth replacing them as the set-up costs would outweigh
the benefit.

Luckily my 7-year old 4-core AMD processor with 8GB of RAM has adequate
power to handle Mageia Linux hosting VMware and two virtual machines: XP
and Windows 10 and that is where I will stay.

Having run numerous operating systems side by side, The sheer bloat
insularity of the latest incarnation leaves me convinced that Microsoft
has developed a death wish. It's a tragedy but so many large firms
sometimes forget who their customers are and paid the price.

Mind you, Kodak are making solutions for a public wanting prints again,
so ...

Did you use the Compatibility tab on the 16-bit programs ?

Paul

I used every published trick in the book, including two compatibility
modes. I would have expected cmd.exe to accept .bat files, which might
have cracked it but ...



I did find a way of eliminating those annoying little arrows on short-cut
icons without losing the right-click start menu.

If anyone is interested I'll post the details here.


--
Mageia 5 for x86_64, Kernel:4.4.16-desktop-1.mga5
KDE version 4.14.5 on an AMD Phenom II X4 Black edition.

On 2/10/16 04:48, pinnerite wrote:
Under XP it has to 'talk' to a 32-bit exe program through which it
conditions text before sending it to the printers. That program executes
properly under Windows 10 but the 16-bit program can no longer find it.

Other often used 16-bit programs produce error messages that make no sense.
It is not worth replacing them as the set-up costs would outweigh the
benefit.

Did you give up too soon? Mind to show us the errors?

--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa