> Bear with me Wolf with me :-)
> Sound cards for example are activated often times by games. > I have the PCI version of the soundblaster 16 and > it works under freedos, but not without a strange TSR. MPXPLAY now works without this strange TSR (ES1371 and ES1373 chips only, test if you are interested). > Can a 32 bit or 64 bit version of freedos solve the driver conflict issue? No. > In NT land, in theory, there are well defined APIs/ABIs and > no direct hardware control by application programs. "well defined" means GUI usage API inside drivers (!!!) and many MiB driver size for just 1 chip or a very small family of chips. > I've tried the 2039 kernel to no avail, the problem still persists. > just wonder if someone has solved this problem already and what was causing Didn't you answer your question just above ? ;-) -- ~~~ wow ~~~ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
