Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #28738
| From | John Speth <johnspeth@yahoo.com> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Codewright Failure |
| Date | 2019-08-02 21:33 -0700 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <qi32qs$12an$1@gioia.aioe.org> (permalink) |
| References | <o858ar$otd$1@dont-email.me> <ApadnYCOnp5Rpd7AnZ2dnUU7-KXNnZ2d@giganews.com> |
I'm also a long time user of Codewright (version 4.0e from 1996). No other editor has satisfied me in terms of getting the code written quickly. I've carried it forward on all the windows versions since 1996. Each version of windows made CW work a little worst but MS seemed to fix the little oddities as windows did incremental updates. It works real nicely with windows 10. You don't need the installer if you have a prior installation. All you need to do is copy the directory tree verbatim TO THE SAME DRIVE AS the ORIGINAL. If you can't keep the same drive, you'll need to hand edit the .ini files that refer to the drive letter before you run it on the new computer. Problems I've observed with the different windows versions are: - It stalls loading during the splash screen. Sometimes it eventually continues after 10 minutes or so, sometimes never. Killing it and restarting it usually fixes that problem. I use Notepad++ as a backup in case I can't get CW to load. - It screws up key repeat timing sometimes when it loads. I have not found a permanent fix to that but I think if you allow loading to happen on a mostly inactive computer (very low CPU load), the timing will be right. This problem is the most annoying because it's not always easy to make it work right. - The help system is dead. It relies on .hlp files which are now gone forever. I never missed it.
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Codewright Failure rickman <gnuarm@gmail.com> - 2017-02-16 17:17 -0500
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2017-02-16 18:18 -0800
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-02-16 21:36 -0500
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2017-02-17 10:11 -0800
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-03-24 15:40 -0400
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2017-03-24 12:54 -0700
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-03-24 16:10 -0400
Re: Codewright Failure George Neuner <gneuner2@comcast.net> - 2017-03-24 22:50 -0400
Re: Codewright Failure rickman <gnuarm@gmail.com> - 2017-03-25 15:39 -0400
Re: Codewright Failure George Neuner <gneuner2@comcast.net> - 2017-03-26 04:55 -0400
Re: Codewright Failure David Brown <david.brown@hesbynett.no> - 2017-03-27 10:05 +0200
Re: Codewright Failure Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-27 14:27 +0300
Re: Codewright Failure David Brown <david.brown@hesbynett.no> - 2017-03-27 14:01 +0200
Re: Codewright Failure Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-27 19:41 +0300
Re: Codewright Failure "David Eather" <eather@tpg.com.au> - 2017-02-18 23:12 +1000
Re: Codewright Failure "David Eather" <eather@tpg.com.au> - 2017-02-18 23:13 +1000
Re: Codewright Failure mrfirmware <mrfirmware@gmail.com> - 2017-03-22 09:32 -0700
Re: Codewright Failure "roricka" <137631@EmbeddedRelated> - 2019-08-01 14:09 -0500
Re: Codewright Failure Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-01 15:51 -0700
Re: Codewright Failure Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-10 15:30 -0700
Re: Codewright Failure John Speth <johnspeth@yahoo.com> - 2019-08-02 21:33 -0700
Re: Codewright Failure quantumankh@gmail.com - 2020-02-09 22:17 -0800
csiph-web