1. RE: BLISS
- Posted by kbochert at ix.netcom.com Jul 10, 2002
- 350 views
-------Phoenix-Boundary-07081998- Hi jordah ferguson, you wrote on 7/10/02 4:52:01 AM: > >i have had trouble with BLISS examples. i downloaded the dll just as you >said in your instructions and loaded carefully the way u said. > >i now get windows errors. saying the program caused an invalid...@##@$ >whatever. i know i haven;t given enuff info of what is going on. i'll >keep you informed meaN while repeat the instructions for getting the >examples to work. i use win98 SE > >jordah I also am using Win98 SE. As an experiment I just downloaded the bliss package and extracted it into a temporary directory. I drag & dropped hello.bls onto bliss.exe and it worked perfectly. There is one small anomaly that worries me. The released version was compiled with Watcom and it puts up a box with a white background. The LCC compiled version puts up a box with the default (sort of putty colored) background. The interpreters role is just to correctly call the DLL, so I'm at a loss to explain this difference and the folks at IUP have yet to respond. More details may be helpful. Karl Bochert -------Phoenix-Boundary-07081998---
2. RE: BLISS
- Posted by jordah ferguson <jorfergie03 at yahoo.com> Jul 18, 2002
- 358 views
Hi Karl, I have had problems trying to get BLISS to work on MY PC, win98 SE. i downloaded the iup library and tried it failed. i then checked one of the examples and found out the lib was pointing to a dll found on e:\. anyway i corrected this and bliss still crashed. I decided to make a small basic win32lib program, that didn't do the trick, I went on to create an API app, Still nothing. so i'm just puzzled as to what i have to do to make bliss work. This is all i get. BLISS caused an invalid page fault in module BLISS.EXE at 015f:0041737e. Registers: EAX=00000000 CS=015f EIP=0041737e EFLGS=00010202 EBX=00428f44 SS=0167 ESP=0057fa60 EBP=0059d550 ECX=0059d550 DS=0167 ESI=00000000 FS=21ef EDX=00428f80 ES=0167 EDI=0057fa64 GS=0000 Bytes at CS:EIP: 8a 06 88 07 3c 00 74 10 8a 46 01 83 c6 02 88 47 Stack dump: 0057fa64 0042fa10 0041750d 755c3a63 70697a6e 00000000 81a414d4 00000200 00000000 0057fb05 77650000 bff7a500 00000001 0057fb49 00010221 0057fad0 jordah ps. If what i read in the docos is so, then i'm really interested in the addition of structures and dot notation. its a shame we cannot bind. kbochert at ix.netcom.com wrote: > -------Phoenix-Boundary-07081998- > Content-type: text/plain; charset=ISO-8859-1 > Content-transfer-encoding: 8bit > > Hi jordah ferguson, you wrote on 7/10/02 4:52:01 AM: > > > > >i have had trouble with BLISS examples. i downloaded the dll just as you > >said in your instructions and loaded carefully the way u said. > > > >i now get windows errors. saying the program caused an invalid...@##@$ > >whatever. i know i haven;t given enuff info of what is going on. i'll > >keep you informed meaN while repeat the instructions for getting the > >examples to work. i use win98 SE > > > >jordah > > I also am using Win98 SE. As an experiment I just downloaded the bliss > package and extracted it into a temporary directory. I drag & dropped > hello.bls onto bliss.exe and it worked perfectly. > > There is one small anomaly that worries me. The released version was > compiled with Watcom and it puts up a box with a white background. > The LCC compiled version puts up a box with the default (sort of > putty colored) background. > > The interpreters role is just to correctly call the DLL, so > I'm at a loss to explain this difference and the folks > at IUP have yet to respond. > > More details may be helpful. > > Karl Bochert > > > -------Phoenix-Boundary-07081998--- >