OS2 World.Com Forum

Subject  :  fixpack problems
Author  :  cyber manic cynic@ptt.yu
Date  :  09 May, 2006 on 08:29
Hi, I've got a DEC HiNote VP700 (PI MMX 233MHz, 64Mb, 1.4Gb) and I was put old good Warp 4 Merlin (first release, FP0 level). Installation is normal and Warp FP0 runs on it just normaly.
Even FP15 installs normaly, but when finished (after reboot normaly service locked files too) but Warp is not longer startable. On boot it showe trap 000D message and stop. Boot to comand line (ALT+F1, F2) is same.
I can boot with disketes but not sure what to do, I was replace whole directories (c:\os2\dll, c:\os2\boot, c:\os2, c:\..) with files from some backups at FP5 level and bootable floppies, and I was have bootable Warp (ALT+F1, F2 was still leed to trap 000D) that was able to install SDD, WapVision, Mozilla, XWP and everything was working nice almost 2 days when it crashed so weird that os2 fdisk (boot from floppies) wasnt able to recognise partition.
So, I supposed that was might be a memory problem, install again, fixpack it to FP15 and remove all memory except build base 16 Mb. Nothing changed, trap 000D in any combination.
As I have several machines running FP15 without any trace of problems from 486DX4 to PIII Im really confused, I try again to replace files but havent luck to got right combination. Now I install Warp again and think about got a FP5 to try.
Does anyone have any idea, any similar experience, or maybe know excatly how to avoid problems ?
Please help, I'm really frustrated because stupid Win98 work on other partition pretty happy.

Subject  :  Re:fixpack problems
Author  :  warpcafe warpcafe@yahoo.de
Date  :  09 May, 2006 on 16:20
Hi,

heck - I don't remember it exactly, but starting with FP14 there was some major change in the contents of warp FPs. I believe it to be the "LVM instead of FDISK" but I'm not sure if also there was something like "device driver fixpak is incorporated" which may lead to drivers getting installed that give problems later.
Most likely, I suppose the problem to be rather disk-, controller- or driver-related. After installing Warp4 GA from scratch, try to use DANI drivers for the disk stuff and/or JJSCDROM for any CD drives. Try to incorporate that into the boot floppies so it will get written into the \os2\boot\config.x file (which is the one used for Alt-F1;F2).
Once that works, install FP15 and before rebooting check if it has "done something" to config.sys. This should preserve teh "alternate" drivers for drive access - if ever that is causing the problem.
Not a perfect solution, but that's what I would try based upon what you described here... maybe other gurus on the forum here have better (faster?) suggestions..? Ideas, anyone?

HTH
Greetings
Thomas


Subject  :  Re:fixpack problems
Author  :  Fahrvenugen
Date  :  09 May, 2006 on 20:03
Trap 000d's... they can be a pain.

I could be wrong, but I think there were some issues with the 14.100 kernel (fixpak 15 level) and Pentium Pros (or am I recalling another kernel revision? I can't recall).

Anyways, you might want to give Kernel revision 14.103a a try (of course keep a backup of your current kernel in case it makes things worse):

http://www.os2site.com/sw/upgrades/kernel/w420050317.zip

Second thing, traps can sometimes be caused by drivers such as ibm1s506 (try Danis506 instead), the CD driver (as mentioned, try the JJSCDROM), and I've also seen from time to time the com.sys driver causing problems (to test, try REMing out the com.sys and vcom.sys).

Fixpak 15 also split off the device drivers from the fixpak, and put them in a separate fixpak. So, you may need to install the Device Driver Fixpak 2. Look for my post at:

http://www.os2world.com/cgi-bin/ultraboard/UltraBoard.cgi?action=Read&BID=62&TID=1102&P=1#ID1102

for info on this.

Check the config.sys for any drivers which aren't needed, and REM them out (for examle, if you're on an IDE system, make sure there aren't any SCSI drivers trying to load up, etc).

Revert to standard VGA for testing. If there's something wrong with a video driver not working with the video card, VGA will usually work at least for testing purposes. Also, for testing purposes, put 64 megs or less memory in the system (but it sounds like you're already doing that).

And if you've got OS/2 installed and it still isn't working, another thing to try is disconnect any hardware which isn't strictly needed for boot. I had one machine years ago where the CD Rom unit for some reason would cause Warp to trap, and I never did figure out why. It would boot fine without the CD Rom connected, so that piece of hardware ended up getting replaced with a different unit which worked fine.

Good luck!


Subject  :  Re:fixpack problems
Author  :  cyber manic cynic@ptt.yu
Date  :  18 May, 2006 on 07:39

Fahrvenugen (09 May, 2006 20:03):
Trap 000d's... they can be a pain.

This goes to my tagline files. It is like twilight zone. )))

>I could be wrong, but I think there were some issues with the 14.100 kernel

It is'nt a kernal, work with FP15 one.

>Second thing, traps can sometimes be caused by drivers such as
>ibm1s506 (try Danis506 instead), the CD driver (as mentioned, try
>the JJSCDROM), and I've also seen from time to time the com.sys
>driver causing problems (to test, try REMing out the com.sys and
>vcom.sys).

You are guru... You pointed right... I've use SIO replacement and Daniela's driver when I was running backups, so I replace ibm1s506 and add SIO and after that FP15 update was normaly.

BUT... Combination of ALT+F1, F2 during boot lead to trap 000D even with Daniela's driver and SIO (or with rem com completly). I wasn't try JJSCDROM still, because in normaly boot it not make problems.
I've manualy analyse c:/config.sys and OS2/Archive/0x config.sys and even replace 0x by normaly used config and everything without success. It trap before danis606 show info about drives (swich /VL).

>Check the config.sys for any drivers which aren't needed, and REM them out
>(for examle, if you're on an IDE system, make sure there aren't any SCSI
>drivers trying to load up, etc).

This is stage I will try now, try to rem out more and more lines. But I not know what 'boot to command line' use that normal boot not.

> Revert to standard VGA for testing. If there's something wrong
>with a video driver not working with the video card, VGA will
>usually work at least for

I've installed SDD, but after applying FP 15, so it is irrelevant. Command line boot wasn't work before SDD.

I'm have working Warp FP15 right now, but without ALT+F1, F2 bootable again, I'l not feel safe to mess arround with system. I've have situation when bootin from floppys, it says that drive has dirty flag but chkdsk wont execute completly. This is laptop device and I cann't boot from any other HDD and coorect errors like i used in such situtations. ((

Just to say that ALT+F1, F2, was work before applying FP15, and after applying FP15 stop.
Probably I should restore something from backuped files but I do not know what, which part may prevent 'command line to boot'.

>Good luck!

Help me again. ))


Subject  :  Re:fixpack problems
Author  :  Fahrvenugen
Date  :  18 May, 2006 on 17:44
Hi,

If you have OS/2 booting to the desktop properly without any Traps, but it does not work for ALT-F1, F2 (boot to command line), then it is probably something in the c:\OS2\BOOT\CONFIG.X file that is causing the system to TRAP.

Try making some of the same changes you made to your main CONFIG.SYS file to the c:\os2\boot\CONFIG.X file and see if that helps.

If you're still having trouble, it might be easiest to just create another boot menu option which will boot to the command line on the ALT-F1 boot menu.

There is more information about how to create a new option on the boot menu at:

http://www.os2voice.org/VNL/past_issues/VNL0898H/vnewsf2.htm

But, a quick rundown of what to do, or instructions which may be successful in getting a "boot to command prompt" option working for you.

1. Boot into OS/2 normally, open a command window, change into your c:\os2\boot directory.

2. Type:

attrib -r c:\os2\boot\altf1bot.scr

This will make the ALTF1BOT.SCR file so that you can write to the file

3. Edit the ALTF1BOT.SCR file in your favourite text editor (I usually use E.EXE), add a line something like:

E) Emergency Boot to Command Prompt

There may be nothing in this file, that is normal. Save the file with the new information

4. Exit out of your editor, and from the command prompt, copy your working config.sys into the c:\os2\boot folder with an extension like .e (or pick any letter other then C, M, V, X, 1, 2 or 3) Example:

copy c:\config.sys c:\os2\boot\config.e

5. Edit the c:\os2\boot\config.e file, find the line:

PROTSHELL=C:\OS2\PMSHELL.EXE

and change it to:

PROTSHELL=C:\OS2\cmd.exe

Next find the line:

SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE

And change it to:

SET RUNWORKPLACE=C:\OS2\cmd.exe

Save the config.e file.

Shutdown and reboot, using the ALT-F1 option. Now you should see additional menu item at the bottom of the screen:

E) Emergency Boot to Command Prompt

Hit "e" on your keyboard, and see if it boots to a command prompt.

If this works for you then there is no need to mess further with the Alt-F1, F2 trap issues. Just use the new "e" (or whatever letter you chose) to get to the command prompt.

Hope this helps


Subject  :  Re:fixpack problems
Author  :  cyber manic cynic@ptt.yu
Date  :  18 May, 2006 on 18:19

Fahrvenugen (18 May, 2006 17:44):
If you have OS/2 booting to the desktop properly without any Traps, but it does not work for ALT-F1, F2 (boot to command line), then it is probably something in the c:\OS2\BOOT\CONFIG.X file that is causing the system to TRAP.

Try making some of the same changes you made to your main CONFIG.SYS file to the c:\os2\boot\CONFIG.X file and see if that helps.


I was try with original c:/config.sys but behave was identical.


Fahrvenugen (18 May, 2006 17:44):
But, a quick rundown of what to do, or instructions which may be successful in getting a "boot to command prompt" option working for you.
3. Edit the ALTF1BOT.SCR file in your favourite text editor (I usually use E.EXE), add a line something like:
E) Emergency Boot to Command Prompt
Hope this helps

Hey, I wasn't know that ! I'l try, but not today... Today stupid computer decided to Warp will not be startable. It happened like previous time, but then I wasn't sure I wasn't mess something up (like rename config.sys instead of copying). But now im rock solid sure that last shutdown was normal, and I wasn't change in c:\config.sys anything for two days.
On boot it says that there is no c:\config.sys, and that cann't find alterantive config.sys either. ALT+F1 does not work !!! and boot from floppies created for install does not see any of partitions (it should be c:HPFS and d:DOS), fdisk load almost year and also do not see any of partitions. If I wasn't think that this is a just twilight zone or simple nightmare, I would be afraid. Very afraid. I will try to make service floppies and try to boot from them later, or tomorow and give a try. If they can not help me, I will be forced again to delete partition, create it again and install Warp again, and again. This does not have sense...

If anyone want to give You laptop HiNoteVP700 made by Digital, even for free, and You are /2 user, hit him in head and run away, run for Your life !!!


Subject  :  Re:fixpack problems
Author  :  Sander
Date  :  19 May, 2006 on 20:32

cyber manic (18 May, 2006 18:21):

Fahrvenugen (18 May, 2006 17:44):
If you have OS/2 booting to the desktop properly without any Traps, but it does not work for ALT-F1, F2 (boot to command line), then it is probably something in the c:\OS2\BOOT\CONFIG.X file that is causing the system to TRAP.

Try making some of the same changes you made to your main CONFIG.SYS file to the c:\os2\boot\CONFIG.X file and see if that helps.


I was try with original c:/config.sys but behave was identical.


Double check CONFIG.X compared to CONFIG.SYS again. It should have worked. One suggestion though. Remove everything from CONFIG.X that is not needed for a command line boot. This will simplify things, make for a faster boot to command line, and help future proof things against some hardware changes you might make.


Subject  :  Re:fixpack problems
Author  :  Stuart srtgray@clara.net
Date  :  20 May, 2006 on 09:07
The other thing to do, when you have a working boot, is run "arcinst" from the command line. This will update the config.x automatically to the latest working version.

Subject  :  Re:fixpack problems
Author  :  cyber manic cynic@ptt.yu
Date  :  25 May, 2006 on 14:59

Fahrvenugen (18 May, 2006 17:44):
If you have OS/2 booting to the desktop properly without any Traps, but it does not work for ALT-F1, F2 (boot to command line), then it is probably something in the c:\OS2\BOOT\CONFIG.X file that is causing the system to TRAP.

Try making some of the same changes you made to your main CONFIG.SYS file to the c:\os2\boot\CONFIG.X file and see if that helps.

If you're still having trouble, it might be easiest to just create another boot menu option which will boot to the command line on the ALT-F1 boot menu.

There is more information about how to create a new option on the boot menu at:
http://www.os2voice.org/VNL/past_issues/VNL0898H/vnewsf2.htm
Hope this helps


This is nice, but it does not right point to solve my problem... When my Warp FixPacked to level 15 hang, it does not allow me to do even ALT+F1, so any other boot like simple F2 could not be reached.
Problem is that I can not find what cause problem, it just work until reboot. And nothing big, I just install or run harmless program and in next reboot simply Warp does not boot. There two different behaviour of "do not boot":
1. Trap 000D; I can boot from install floppies and run fdisk, but I can not access partition c: (HPFS) (sys0026 specified disk or diskette cannot be accessed, I can format drive successfully
2. On boot Warp claim that there is no c:\config.sys and that there is no c:\os2\boot\altf1bot.scr, I can boot from install floppies but c: isn't there, fdisk does not work at all. In both cases, boot from DOS diskette and use of IHPFS see c:\config.sys and altf1bot.scr, and does not claim of any problems... i can copy files from c: anywhere...
I was try to use ALT+F2 during boot to see what encounter problem but without success, trap 000D come immediatly and 'no c:\config.sys too...

First problem for applying FP15 was solved successfully by You Fahrvenugen, but I probably can not applying whole FP15, so I plane when I have enough time to try to keep original kernal and loader files to try what will happend.


Powered by UltraBoard 2000 <www.ub2k.com>