Home > Archive > Clipper > June 2006 > blinker5 win2000 gpf
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
blinker5 win2000 gpf
|
|
|
| app c53b blinker5, no mouse [pure old text app], makes gpf [quite often]
when run on win2000.
not allways, but sometimes if accidentally mouse is moved.
[everything was ok, untill appeared this new customer with their old
fashioned obsolete win2000 systems].
on winxp it allways runs ok [dos, win98 as well]
blinker support page, as well as dave pearson's faq say "upgrade to
blinker7"
since app is pure text, i don't need any extended functionality, just to
keep it running on most platforms.
does it mean there is no "patch" just to hide/inhibit blinker's mouse funcs
that cause problem?
any comments or advice?
thnx
| |
| Nick Ramsay 2006-06-17, 7:55 am |
| On Tue, 6 Jun 2006 12:24:13 +0200, "sali" <sali@euroherc.hr> wrote:
[snip]
>any comments or advice?
Try to ensure you have the latest (or, even better, WHQL certified)
video drivers.
| |
| vbdasc@yahoo.com 2006-06-17, 7:55 am |
| sali wrote:
> does it mean there is no "patch" just to hide/inhibit blinker's mouse funcs
> that cause problem?
They are Clipper's, not Blinker's.
> any comments or advice?
It may be possible to disable the mouse completely by patching the
compiled .EXE file. Try the following (tested ONLY with Clipper 5.3b).
Replace the following sequence of bytes, using your favorite hex
editor/patcher (hexadecimal notation):
B8 33 35 CD 21 8C C0 0B C3 74 46
with:
B8 33 35 CD 21 8C C0 33 C0 74 46
HTH,
Vassil Daskalov
| |
|
| since sequence is given without offset, does it mean that sequence is
*unique* accros the executable?
is it possible to replace sequence by some "clean" method, like linking in
some dummy inactive replacement routine to replace those "mouseable"?
<vbdasc@yahoo.com> wrote in message
news:1149612453.421202.24040@u72g2000cwu.googlegroups.com...
> sali wrote:
funcs[color=darkred]
>
> They are Clipper's, not Blinker's.
>
>
> It may be possible to disable the mouse completely by patching the
> compiled .EXE file. Try the following (tested ONLY with Clipper 5.3b).
> Replace the following sequence of bytes, using your favorite hex
> editor/patcher (hexadecimal notation):
>
> B8 33 35 CD 21 8C C0 0B C3 74 46
>
> with:
>
> B8 33 35 CD 21 8C C0 33 C0 74 46
>
> HTH,
> Vassil Daskalov
>
| |
| Stephen Quinn 2006-06-17, 7:55 am |
| Sali
You might look for nomouse.obj in your clipper LIB/OBJ directories, this just
stubbed out the mouse routines when linked in.
I can't tell you which library it comes with as my machine with Clipper on it
has karked it
- waiting for a new processor to arrive as I write<g>
Seeing as you have C53 have a look at the LightLib stuff.
HTH
Steve
| |
|
| Best thing is too upgrade to blinker 7
dave
"sali" <sali@euroherc.hr> wrote in message
news:e63l4d$ink$1@ss408.t-com.hr...
> app c53b blinker5, no mouse [pure old text app], makes gpf [quite often]
> when run on win2000.
> not allways, but sometimes if accidentally mouse is moved.
> [everything was ok, untill appeared this new customer with their old
> fashioned obsolete win2000 systems].
> on winxp it allways runs ok [dos, win98 as well]
>
> blinker support page, as well as dave pearson's faq say "upgrade to
> blinker7"
>
> since app is pure text, i don't need any extended functionality, just to
> keep it running on most platforms.
> does it mean there is no "patch" just to hide/inhibit blinker's mouse
> funcs that cause problem?
>
> any comments or advice?
> thnx
>
>
| |
| vbdasc@yahoo.com 2006-06-17, 7:55 am |
| sali wrote:
> since sequence is given without offset, does it mean that sequence is
> *unique* accros the executable?
If you do not use any custom mouse code then yes, it should be unique.
> is it possible to replace sequence by some "clean" method, like linking in
> some dummy inactive replacement routine to replace those "mouseable"?
That sequence can be found in the library TERMINAL.LIB, module
MOUSEIBM. You may be able to extract MOUSEIBM.OBJ using some library
utility, patch it accordingly, and link it to your application. IIRC,
patching object files can be tricky, though. (because they contain
checksum values; blind patching can destroy the checksums).
HTH,
Vassil Daskalov
| |
|
| thnx.
this is something i was looking for.
i had read about it somewhere in the past, but since i had no win2000
systems [and no problems] at that time, i missed it.
"Ross McKenzie" <NoJunk_valusoft@optusnet.com.au> wrote in message
news:44863f77.16489859@news...
> On Wed, 07 Jun 2006 01:31:07 GMT, "Stephen Quinn"
> <steveq@NOSPAMintegritynet.com.au> wrote:
>
>
> Hi Steve and Sali.
>
> Here is the original code for nomouse.obj. Just compile and link
> in....
>
| |
| Stephen Quinn 2006-06-17, 7:55 am |
| Ross
Thanks for that.
Wouldn't you know they sent the wrong CPU and now tell me what I want is no
longer available<sigh>, looks like it's a new motherboard as well (lucky that's
only another $100 which I won't be spending with them<g> ).
CYA
Steve
| |
| Ross McKenzie 2006-06-17, 7:55 am |
| On Wed, 07 Jun 2006 01:31:07 GMT, "Stephen Quinn"
<steveq@NOSPAMintegritynet.com.au> wrote:
>Sali
>
>You might look for nomouse.obj in your clipper LIB/OBJ directories, this just
>stubbed out the mouse routines when linked in.
>
>I can't tell you which library it comes with as my machine with Clipper on it
>has karked it
> - waiting for a new processor to arrive as I write<g>
>
>Seeing as you have C53 have a look at the LightLib stuff.
>
>HTH
>Steve
>
>
Hi Steve and Sali.
Here is the original code for nomouse.obj. Just compile and link
in....
* ÚÄ Program
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
* ³ Application: Calculator 2.0
³
* ³ File Name: NOMOUSE.PRG Stub module for no-mouse ability
³
* ³ Author: Jim Gale
³
* ³ Date created: 10-03-93
³
* ³ Time created: 11:06:04pm
³
* ³ Make File:
³
* ³ Exec File:
³
* ³ Copyright: 1993 by Touchstone Business Creations
³
*
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
* ÚÄ Function
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
* ³ Description: Determime if a mouse if present in the system.
³
* ³ Author: Jim Gale
³
* ³ Date created: 10-30-93
³
* ³ Time created: 09:35:00am
³
* ³ Copyright: Touchstone Business Creations
³
*
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
* ³ Function: CM_IsMouse()
³
* ³
³
* ³ Arguments: none
³
* ³
³
* ³ Return Value: False - no mouse exists in system (NOMOUSE)
³
* ³
³
* ³ See Also:
³
* ³
³
*
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
Function CM_IsMouse()
Return .F.
Function CM_Button()
Return 0
Function CM_Row()
Return 0
Function CM_Col()
Return 0
Function CM_On()
Return .F.
Function CM_Off()
Return .F.
Function CM_Cursor()
Return .F.
Function CM_Init()
Return NIL
Function CM_Wait()
Return Inkey(.2)
Function CM_Exit()
Return NIL
*********************************
Regards,
Ross McKenzie
ValuSoft
Melbourne Australia
valusoft AT optusnet DOT com DOT au
| |
| Karel Zámecník 2006-06-24, 7:55 am |
| I am using Blinker 1.5 without problem on Win2k, WinXP.
Clipper 5.2e + CA Tools.
It is the BEST
<vbdasc@yahoo.com> píse v diskusním príspevku
news:1149691369.783141.249840@h76g2000cwa.googlegroups.com...
> sali wrote:
>
> If you do not use any custom mouse code then yes, it should be unique.
>
>
> That sequence can be found in the library TERMINAL.LIB, module
> MOUSEIBM. You may be able to extract MOUSEIBM.OBJ using some library
> utility, patch it accordingly, and link it to your application. IIRC,
> patching object files can be tricky, though. (because they contain
> checksum values; blind patching can destroy the checksums).
>
> HTH,
> Vassil Daskalov
>
| |
|
| thnx for the info, but think that is hard to force some clipper/blinker
version pair
company adopted and tested clp53b/blnk5 combination, it is realy hard to try
old blinker1?
i found "dummy" mouse functions presented here, to be the most appropriate
fixings!
"Karel Zámecník" <karel.zamecnik@seznam.cz> wrote in message
news:e7euu7$n12$1@news.vol.cz...
>I am using Blinker 1.5 without problem on Win2k, WinXP.
> Clipper 5.2e + CA Tools.
> It is the BEST
>
> <vbdasc@yahoo.com> píse v diskusním príspevku
> news:1149691369.783141.249840@h76g2000cwa.googlegroups.com...
>
>
| |
| Stephen Quinn 2006-06-24, 7:55 am |
| Sali
Blinker 1.0 came with Clipper 5.3
- it's the REAL MODE only linker that replaced RTLink in that version.
HTH
Steve
| |
|
| funny, it seems there was some problems with my news server, i didn't notice
this answer posted till next message having reference to your's arrived [i
am now sending through alternative news server]
lib or exe patching is some kind of last resort [it was very usual method in
the good old dos days, where i used to patch arcade games to gain unlimited
number of lives, simply replacing "dec #location" with "noop" instructions],
but here presented "dummy" mouse lib functions i find as more flexible
solution, not being so "low level"
<vbdasc@yahoo.com> wrote in message
news:1149691369.783141.249840@h76g2000cwa.googlegroups.com...
> sali wrote:
>
> If you do not use any custom mouse code then yes, it should be unique.
>
>
> That sequence can be found in the library TERMINAL.LIB, module
> MOUSEIBM. You may be able to extract MOUSEIBM.OBJ using some library
> utility, patch it accordingly, and link it to your application. IIRC,
> patching object files can be tricky, though. (because they contain
> checksum values; blind patching can destroy the checksums).
>
> HTH,
> Vassil Daskalov
>
|
|
|
|
|