> Sometimes, I suffer from a severe lack of trust in other > programmers. I look at the "Install Check" and see only specific > registers are to be modified and no others are to be destroyed. But > in my head, I think that someone out there may think it is a good > idea to save some time by passing some additional information back > in one of those registers. However, that would be their bug and not > mine. So, I will remove them and not worry about it (very much). :-)
That was one of my problems when I was using INT 2Fh since it doesn't really have a defined technical specification. Sometimes, even with MS programs, even the "Install Check" function will return data in various registers (like a version number or something). When I was using INT 2Fh I needed to be very cautious since I never knew what unexpected things some other program might do. AMIS (and IISP) are rigidly defined so there shouldn't be any "surprises". AMIS also lets you define your own sub-functions and those can work however you want them to, but the defined functions need to follow the specification precisely. In addition, I should also warn you that if you plan on using AMIS in the future you should probably start doing it right away instead of waiting. This is a problem I had with some of the programs I've had out for a long time (since before I started using AMIS). In the old versions of the programs I used INT 2Fh but the newer versions use AMIS (INT 2Dh). The problem is that when I'm trying to install a new version of the program I need to test to see if another copy of the program is already installed, and if so which version it is. To make sure a really old version isn't already installed I need to do both the old (INT 2Fh) and new (AMIS/INT 2Dh) tests. That is both cumbersome and slow and should be avoided. You usually don't want two versions of the same program running at the same time unless they are specifically designed to "cooperate" with each other. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
