lohman@blake.acs.washington.edu (Kevin Lohman) (08/22/89)
I have been working on a program that plays with the colormap to produce a colored canvas and to draw lines in color on that canvas. When I compile the program, I do not get any errors, and it runs without errors also. However, in the window the program is executed from, I get the following message: WIN ioctl number 20006703: Device busy Anyone know what this means and how I can fix it? The program seems to run without errors - so is it just an annoying message? Thanks for any help - Kevin Lohman ################################################# # lohman@blake.acs.washington.edu # #################################################
Kemp@dockmaster.ncsc.mil (09/01/89)
Kevin Lohman writes: > When I compile the program, I do not get any errors, and it runs > without errors also. However, in the window the program is executed from, > I get the following message: > > WIN ioctl number 20006703: Device busy > > Anyone know what this means and how I can fix it? The program seems > to run without errors - so is it just an annoying message? Yes. The June Software Technical Bulletin (p.787) says: "Users can be confused when an application runs properly, but the following error message is returned: WIN ioctl number 20006703: Device busy This message is received because user [sic] has set WIN_SHOW to TRUE when creating a base frame. The function window_main_loop() takes a base frame as an argument. It sets WIN_SHOW to be TRUE for this frame and then calls notify start(). Since the user has set WIN_SHOW to TRUE in window_create(), then window_main_loop() sets WIN_SHOW to TRUE for the second time, and the "Device busy" error message results. Remove this line from window_create() and the error message will go away." I guess that says it all. Dave Kemp <Kemp@dockmaster.ncsc.mil>