Re: XyWin on XP

[Peter Cassidy pcassidy@xxxxxxxx]

Xywriters,

Has anyone come up with a programming trick or command sequence that
allows Xy4 to use Copy (CNTRL-C) and Cut (CNTRL-X) in the Windows
convention and write and read from the corelative Windows buffer which
those commands address?

Peter

On Fri, 18 Nov 2005, Patricia M. Godfrey wrote:

> RJW823@xxxxxxxx wrote:
>
> >
> >My desktop has same processor and RAM. XyWin runs fine.
> >Bob White
> >
>
> We've apparently eliminated CPU and RAM, or at least gross amount of
> RAM. So the next things to look at are BIOS and chipsets. Unfortunately,
> they're harder to find out, esp. in Name Brand systems. The BIOS brand
> and version usually flashes on the screen at the PC boots, but with
> modern screamingly fast systems (before they start trying to load
> Redmond Rubbish), that can fly by too fast to be seen. If you cannot
> catch the name and version, look for the key that you're supposed to hit
> to enter the BIOS (you may well need it sometime, so you should know it
> anyway), and hit it. DON'T do anything once you're in it, just look and
> see; it should say, e.g., AMI BIOS version xx.xxx. Write it down, then
> hit escape and accept "Exit without saving?"
>
> The chipset maker and version should be listed in the docs that came
> with the machine. It also probably appears in Control Panel's Device
> Manager: things like the IDE controller, USB controller, IRQ steering
> will specify whom they're by.
>
> I will check next time I'm in the office and see what the XP box has. If
> we can amass enough data, we may be able to discern a pattern. (If two
> people have the exact same hardware, and one can run XyWin and one
> cannot, then we know that the problem is in some setting, either in XP
> or XyWin. If no one with Brand X BIOS or Chipset can run it, and
> everyone with Brand Y can, we know it's a hardware issue.)
>
> Patricia M. Godfrey
>
>