| Subject | : | starting code in config.sys |
| Author | : | kg |
| Date | : | 31 Aug, 2004 on 16:50 |
| Hi all, I need to start a piece of code to change a wrong bios settings related to serial port . This code must run before COM.SYS loads thanks, |
| Subject | : | Re:starting code in config.sys |
| Author | : | abwillis abwillis@comcast.net |
| Date | : | 31 Aug, 2004 on 19:26 |
| Yes you can run an exe but it will start after the device drivers are loaded. I don't know of a way around that, though I think there are some things that will halt the config.sys to run stuff from the command line before continuing but I am not sure what stage it would stop it at (i.e. during device driver load or after). Veit has written a program that will load bios code, don't remember the name but it is on hobbes. Andy |
| Subject | : | Re:starting code in config.sys |
| Author | : | Bart |
| Date | : | 31 Aug, 2004 on 20:49 |
| I believe you can use the run= command for the config.sys to run your executable. The problem you may have is the processing order of the config.sys. It is a multi-pass startup and the run statement is near the end of the priority list. (your com.sys will still start first) Page 15 (pdf page 43) of this link has a list of the startup order. Regards, |
| Subject | : | Re:starting code in config.sys |
| Author | : | kg |
| Date | : | 01 Sep, 2004 on 09:13 |
| thanks for the pdf ... so i have to do a dev driver just to make a write in the BDA ! do you know where can i find a base OS2 device driver code ? and how to build it (plateform, compiler and tools )? kg |
| Subject | : | Re:starting code in config.sys |
| Author | : | Cris |
| Date | : | 01 Sep, 2004 on 09:31 |
| Hi, wouldn't it be simpler to NOT START AT ALL com.sys and company (i.e. temporarily rem it out of config.sys), run your code (with a RUN= statement in config.sys if you want), restore com.sys and company (vcom.sys etc.) and reboot? Sorry if I missed something obvious. Bye Cris |
| Subject | : | Re:starting code in config.sys |
| Author | : | abwillis abwillis@comcast.net |
| Date | : | 01 Sep, 2004 on 14:47 |
| He is not flashing the bios, merely updating it so it has to be done each boot. I don't know if it would even hold through a warm reboot or not ... maybe. Andy |
| Subject | : | Re:starting code in config.sys |
| Author | : | abwillis abwillis@comcast.net |
| Date | : | 01 Sep, 2004 on 14:48 |
| See if http://hobbes.nmsu.edu/pub/os2/util/mboard/lmicro.zip does what you need. Andy |
| Subject | : | Re:starting code in config.sys |
| Author | : | kg |
| Date | : | 01 Sep, 2004 on 15:31 |
| My problem is to find a way to write the I/O adress of my second com port at MEM @ 0040:0002 before COM.SYS start This has to be done at each boot. Actually i do it manually with debug ( e 40:02 F8 02 ) then i do a warm reboot with int19 to start OS2 and it's really boring to do that each time. Thanks Andy, I'am still looking for a solution and idea are still welcome !! kg, |
| Subject | : | Re:starting code in config.sys |
| Author | : | abwillis abwillis@comcast.net |
| Date | : | 01 Sep, 2004 on 20:08 |
| I don't know for certain but I figure if you sent an email to Veit he would likely send you the source code unless he has some constraint preventing it. I found the file I was thinking of that stops the config.sys but it stops it with an exec which is after the device drivers are installed. Andy |
| Subject | : | Re:starting code in config.sys |
| Author | : | devnul |
| Date | : | 01 Sep, 2004 on 23:21 |
Maybe you consider my suggestion unsportive. But how about adding a seperate COM adapter into one of your (PCI or ISA) slots and disabling COM2 at your Motherboard ? Guess thats ways easier |
| Subject | : | Re:starting code in config.sys |
| Author | : | kg |
| Date | : | 02 Sep, 2004 on 09:20 |
it's because i see the problem with this kind of device ![]() |
| Subject | : | Re:starting code in config.sys |
| Author | : | warpcafe warpcafe@yahoo.de |
| Date | : | 03 Sep, 2004 on 09:47 |
| Hi, maybe you should give a try to SIO.SYS instead of COM.SYS. The URL is www.gwinn.com but I wasn't able to reach it at the moment... anyway a "special edition" of it is included with eCS1.1... otherwise it's shareware which requires registration but even if you don't consider registrating it, it will allow you to check if problems could be resolved by using it... and then register it... Sorry if I completely misunderstood what you were trying to do! Greetings |
| Subject | : | Re:starting code in config.sys |
| Author | : | kg |
| Date | : | 07 Sep, 2004 on 11:10 |
| Finally i solved my problem i have downloaded the ddk , with the help of a sample code, i have done a tiny driver to do that .thanks |
| Subject | : | Re:starting code in config.sys |
| Author | : | Kim |
| Date | : | 07 Sep, 2004 on 12:19 |
Something that you would like to share? |
| Subject | : | Re:starting code in config.sys |
| Author | : | kg |
| Date | : | 07 Sep, 2004 on 13:28 |
| yes, a good starting point is here.. http://hobbes.nmsu.edu/cgi-bin/h-browse?sh=1&dir=//pub/os2/dev/drivers phymem is a simple and good sample even if you are new to OS2 dev and DDK |