| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | your utils using angel |
>> No, I had not heard anything from anyone about that situation. I don't real >> understand what an ntvdm error is. > NTVDM = NT virtual Dos machine > ntvdm errors occur when 16 bit applications do something 'screwy', for > example access some inner workings that conflict with windows. I've seen that sort of thing myself when I test utility programs, but have not ever seen it occur while running one of my igms in LORD. There are some specific commands in the ANGEL toolkit that work fine if you are inside LORD igms when they occur. But if you ran the same command in the igm's Setup utility, for example, it would immediately cause WinXP to shut down the window down. With exception of work done last night and early this morning on Lord Gambling Casino, Lord Holidays, Gem Trader, and Outlands Tavern, all of my Lord programs are fully up-to-date on the Castle Camelot web-site. You might retry some of the igms with their most up-to-date version, and let me know if the problems show up again. Right now, I don't have enough information to try to reproduce a problem, or figure out what to look at. The only person who can fix a problem if it is inside the ANGEL toolkit itself is Jimmy Rose. And I've not seen him around in these echoes in a long time. I think he's a college student, and he may simply be too busy to work on his toolkit. > the pawn shop in particular causes this error in some of the shop sections, > and i've seen it in a few other igms. i didnt say anything because they were > in beta, i probably should have reported them sooner. i thought i simply had > older betas and they were fixed. I appreciate the information but right now I can't do anything about those problems. Just not enough details to pinpoint what might be causing the problems. It would be nice to know for example if the same NTVDM error occurred in the same igm on two separate bbs software programs. That would probably indicate the problem was related to interaction between IGM and BBS software and the Operating system. Not that it would help that much on my end knowing that was the case. But if the problem can be reproduced then Dennis Collins or someone else probably can identify the gremlin and kill it for me. Donald. --- BBBS/LiI v4.01 Flag* Origin: Prism bbs (1:261/38) SEEN-BY: 10/1 3 14/300 34/999 90/1 106/1 120/228 123/500 134/10 140/1 222/2 SEEN-BY: 226/0 236/150 249/303 261/20 38 100 1381 1404 1406 1410 1411 1418 SEEN-BY: 266/1413 280/1027 320/119 393/68 633/260 262 267 285 690/682 734 SEEN-BY: 712/848 800/432 801/161 189 2222/700 2320/100 105 109 200 303 2905/0 @PATH: 261/38 633/260 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.