I'm just trying out MFC Client 139 over pro-iv 4.6 1.07.
Every now and again the kernel prompt does not recognise that I have typed in a function name and keeps reprompting.
I have to kill the windows task to get out. Anybody seen this ? - I have to say that the official response from Pro-iv Support has not been very informative.

139 Client Kernel prompt bug
Started by Tony White, Jan 28 2000 10:06 AM
3 replies to this topic
#2
Posted 28 January 2000 - 10:46 AM
This has happened with ye old GUI environment for quite some time. I've found this tends to occur if you interrupt a running function. When the command line box appears if you persist with entering the function eventually it will decide it's about time it started working and execute it.
I believe the Pro-iv response to this one is: Due to the Eastern winds blowing over the Sahara in August the scorpions found in that area bring little grains of sand to your PC which they use to fill up your keyboard buffer and because scorpions are not bugs this is not a problem. :-)
I believe the Pro-iv response to this one is: Due to the Eastern winds blowing over the Sahara in August the scorpions found in that area bring little grains of sand to your PC which they use to fill up your keyboard buffer and because scorpions are not bugs this is not a problem. :-)
#3
Guest_trev_*
Posted 01 February 2000 - 10:41 AM
You don't state which platform, but If NT, this is a service problem. R200 cures most instances of it. we had no diffulties at all going from 107 to 200, but I will say here, we only use Pro-ISAM files. Client 200/201 is a different matter altogether. Nightmare.
#4
Posted 01 February 2000 - 12:12 PM
Thanks for your replies folks. Good to know that this is an actual problem then, and not just me !
The platform by the way is an IBM RS6000 H70 running AIX 4.3 with Pro-iv 4.6 r107. The 139 client is on windows 95.
I have heard since, that you should be able to clear the mis-behaving kernel prompt's buffer by typing return several times, then retyping the function name.
Unfortunately this has not worked, and my office rings to the sound of frustrated developers crashing out of GUI sessions!
I'll probably be moving our live systems over to r200 soon, so hopefully this may solve it. (Or is r200 likely to unleash a pile more problems ?)
Rgds
Tony White
The platform by the way is an IBM RS6000 H70 running AIX 4.3 with Pro-iv 4.6 r107. The 139 client is on windows 95.
I have heard since, that you should be able to clear the mis-behaving kernel prompt's buffer by typing return several times, then retyping the function name.
Unfortunately this has not worked, and my office rings to the sound of frustrated developers crashing out of GUI sessions!
I'll probably be moving our live systems over to r200 soon, so hopefully this may solve it. (Or is r200 likely to unleash a pile more problems ?)
Rgds
Tony White
Reply to this topic

0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users