Return-Path: Received: from darkside. (darkside. [210.8.201.180]) by mail. (Weasel v1.20) for ; 03 July 2001 01:00:00 From: "Digest" To: "OS/2GenAu Digest" Date: Tue, 03 Jul 2001 01:00:00 +1000 (EDT) Reply-To: "OS2GenAu" Priority: Normal X-Mailer: CASMailer 1.0 for OS/2 Warp PPC 1.05/G4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: No. 107 Message-ID: <200107030100.000029G6atmail.> Date:- 03 July 2001 1================================================ From: Trevor Clarke Subject: [os2genau] dead dll's Date: Mon, 2 Jul 2001 13:35:44 +1000 Arh! Does anybody know how to extract dl_ files from a fixpack? This will save me a lot of stuffing around..... 2============================================= Date: Mon, 02 Jul 2001 10:10:34 +0200 From: Kris Steenhaut Subject: Re: [os2genau] dead dll's Trevor Clarke schreef: > Arh! > > Does anybody know how to extract dl_ files from a fixpack? This will save > me a lot of stuffing around..... > unpack olala.dl_ olala.dll or UNPACK A:olala.dl_ C:\OS2 When unpack2 isn't in the path (as it should be), you'll have to specify the path ofcoz. Type help unpack at an os2 prompt to learn more about this little matter. -- Groeten uit Gent, Kris 3============================================= Date: Mon, 2 Jul 2001 04:18:45 -0400 From: Chris Neeson Subject: [os2genau] Lost desktop after a trap e There are a few ways of getting back your desktop. One which MIGHT work is: - boot from floppy to a OS2 prompt, or even to an OS2 prompt during boot from the hard drive - check your bootdrive\OS2\ARCHIVES directory it will have subdirectories in which OS2 stored backups of OS2.INI, OS2SYS.INI, and the DESKTOP DIRECTORY structure ( WITH THE EAs - I think! ) during the original install, and possibly at each boot ( depending on your DESKTOP archiving option ) There will be a 0X subdirectory, and I'd expect a 01 subdirectory as well If you've been archiving the desktop at boot, there will also be 02 and 03. - you can use TEDIT to display the contents of files in the desktop archives, or TYPE them if you like - The ARCHIVES.$$$ file contains a list of desktop archives - The OS2.KEY file contains a SEQUENCED list of files in each desktop 'archive', and their names ( so the first file in the list is archived as filename '0', the second as filename '1' etc ) - The KEYS.$$$ file in each archive directory structure also seems to contain a list of archive filenames, with the precise location of the desktop file which was archived into it - so you can see - which desktop archive is the most recent ( from the file and directory dates ) - which file in which archive is a copy of OS2.INI, or OS2SYS.INI. - what the DESKTOP directory ( folder ) structure looked like at each desktop archive ( NOTE: IF YOU USED A FAT SYSTEM ON YOUR BOOT DRIVE, LIKE ME, OS2 CAN ONLY USE 11 CHARACTERS FOR DIRECTORY NAMES RELATED TO DESKTOP FOLDERS OS2 SHOVES THINGS LIKE LONG FOLDER NAMES INTO EXTENDED ATTRIBUTES THIS IS WHERE BOOTING TO OS2 IS IMPORTANT, SO YOU CAN ACCESS THE EAs WHEN YOU MANIPULATE FILES AND DIRECTORIES ) - then you need to decide what to do - IF you're not getting any messages about OS2.INI, OS2SYS.INI, They would appear to be OK The DESKTOP EAs might be 'lost' ( did you get any messages about lost EAs during the CHKDSK? ACTUALLY, ITS WORTH RUNNING A CHKDSK /F ON THE BOOTDRIVE AND SEEING WHAT YOU GET ) This MIGHT be fixed by using OS2's XCOPY to copy the FOLDER structure from the DESKTOP archive of your choice, to the current bootdrive\DESKTOP directory - using OS2 XCOPY will copy the archived desktop EAs back to the actual DESKTOP directory structure eg XCOPY bootdrive\OS2\ARCHIVES\01 bootdrive\DESKTOP /s /v /e ( MAKE ANOTHER XCOPY OF THAT DESKTOP ARCHIVE STRUCTURE INTO SOME ADHOC DIRECTORY, BEFORE YOU REBOOT, SO YOUR FALLBACK POSITION IS ITSELF RECOVERABLE ) - ELSEIF ( well, anything else ) - it might be worth copying the desktop archive files which represent OS2.INI ( typically file '0' ) and OS2SYS.INI back to bootdrive\OS2 - ELSEIF No more ideas. Regards Chris PS: the complexity of this method is, of course, is why somebody made and markets a utility to manage your desktop archives. -------------------------- Stan emailed -------------------------- The saga continues, it seems I may have a corrupt ini file, basically a trap e occured why playing a .wav file on my viaudio ac97 on board soundcard. After the reboot has some errors on som.log in my smartsuie directory caused by the chkdsk, but all I got was a black screen with the pointer, remmed out a lot of stuff just to get a basic system going, restoring desktop no go.= Everything is still there any way I can get my desktop back without re-installing. tia Stan Pallis 4============================================= From: "Robert Traynor (BobT)" Date: Mon, 02 Jul 2001 18:43:38 +1000 (EST) Subject: Re: [os2genau] Lost desktop after a trap e Hi, Good Ideas, but I would also add anywhere, to your config.sys:- SET desktop=\DESKTOP ie in MY case it is SET desktop=D:\DESKTOP This can't do any harm and might just help as well. Regards, BobT. On Mon, 2 Jul 2001 04:18:45 -0400, Chris Neeson wrote: >There are a few ways of getting back your desktop. > >One which MIGHT work is: > >- boot from floppy to a OS2 prompt, > or even to an OS2 prompt during boot from the hard drive > >- check your bootdrive\OS2\ARCHIVES directory > > it will have subdirectories in which OS2 stored > backups of OS2.INI, OS2SYS.INI, and the DESKTOP > DIRECTORY structure ( WITH THE EAs - I think! ) during the original > install, and possibly at each boot ( depending on your > DESKTOP archiving option ) > > There will be a 0X subdirectory, and I'd expect a 01 > subdirectory as well > > If you've been archiving the desktop at boot, > there will also be 02 and 03. > >- you can use TEDIT to display the contents of files > in the desktop archives, or TYPE them if you like > >- The ARCHIVES.$$$ file contains a list of desktop archives > >- The OS2.KEY file contains a SEQUENCED list of files in each > desktop 'archive', and their names > ( so the first file in the list is archived as filename '0', > the second as filename '1' etc ) > >- The KEYS.$$$ file in each archive directory structure also > seems to contain a list of archive filenames, with the precise > location of the desktop file which was archived into it > >- so you can see > > - which desktop archive is the most recent > ( from the file and directory dates ) > > - which file in which archive is a copy of OS2.INI, or > OS2SYS.INI. > > - what the DESKTOP directory ( folder ) structure > looked like at each desktop archive > ( NOTE: IF YOU USED A FAT SYSTEM ON YOUR > BOOT DRIVE, LIKE ME, OS2 CAN ONLY > USE 11 CHARACTERS FOR DIRECTORY > NAMES RELATED TO DESKTOP FOLDERS > OS2 SHOVES THINGS LIKE LONG FOLDER NAMES > INTO EXTENDED ATTRIBUTES > THIS IS WHERE BOOTING TO OS2 IS IMPORTANT, > SO YOU CAN ACCESS THE EAs WHEN YOU > MANIPULATE FILES AND DIRECTORIES ) > >- then you need to decide what to do > > - IF you're not getting any messages about OS2.INI, OS2SYS.INI, > > They would appear to be OK > > The DESKTOP EAs might be 'lost' > ( did you get any messages about lost EAs during the CHKDSK? > ACTUALLY, ITS WORTH RUNNING A CHKDSK /F ON THE > BOOTDRIVE AND SEEING WHAT YOU GET ) > > This MIGHT be fixed by using OS2's XCOPY to copy the FOLDER > structure from the DESKTOP archive of your choice, to the > current bootdrive\DESKTOP directory > - using OS2 XCOPY will copy the archived desktop EAs back to the > actual DESKTOP directory structure > > eg XCOPY bootdrive\OS2\ARCHIVES\01 > bootdrive\DESKTOP /s /v /e > > ( MAKE ANOTHER XCOPY OF THAT DESKTOP ARCHIVE > STRUCTURE INTO SOME ADHOC DIRECTORY, BEFORE > YOU REBOOT, SO YOUR FALLBACK POSITION IS ITSELF > RECOVERABLE ) > > - ELSEIF > ( well, anything else ) > > - it might be worth copying the desktop archive files which > represent OS2.INI ( typically file '0' ) and OS2SYS.INI back > to bootdrive\OS2 > > - ELSEIF > > No more ideas. > >Regards >Chris > >PS: the complexity of this method is, of course, is why > somebody made and markets a utility to manage your > desktop archives. >-------------------------- Stan emailed -------------------------- > >The saga continues, it seems I may have a corrupt ini file, basically a >trap >e occured why playing a .wav file on my viaudio ac97 on board soundcard. >After the reboot has some errors on som.log in my smartsuie directory >caused >by the chkdsk, but all I got was a black screen with the pointer, remmed >out >a lot of stuff just to get a basic system going, restoring desktop no go. >Everything is still there any way I can get my desktop back without >re-installing. > >tia > >Stan Pallis >------------------------------------------------------------------------ > To Subscribe/Unsubscribe go to http://www.os2site.com/list/ ,-._|\ Robert Traynor (BobT) / Oz \ email rtraynoratnetstra dot com dot au \_,--.x/ 5============================================= From: "Robert Traynor (BobT)" Date: Mon, 02 Jul 2001 19:26:14 +1000 (EST) Subject: Re: [os2genau] dead dll's Sorry, Wrong answer. The original request was :- Does anybody know how to extract dl_ files from a FIXPACK? The FIXPACK files are special compressed files and have to be processed to extract all the files first and then you can play with the files you want to locate and unpack. Utility for disk image unpacking (DSKXTRCT.EXE) from Hobbes. Example of use to run against ALL the fixpack files in the same sub dir and extract the LOT, one after the other is:- Dskxtrct /s:*.?DK /t:n:\tcp /ra /c This extracts all files from ALL the fixpack compressed files to drive N: and sub dir \TCP and will keep the directory structure intact. The "*.?DK" refers to the warp fixkpack files, which usually start with XR_ etc. The extension is usually a number 1 to 9 and if there are a LOT of fixpack archive files, the the number gives way to the alphabetic characters a to z. However, some fixpacks have different extension rules, so adapt the command to suit. I prefer to use (if it works, sometimes it won't due to nature of fixpack preparation) the "diunpack" utility. I use this to make my own fixpack CD's. Unfortunately I cannot remember where I got it from. Email me privately if you want it. Instead of running "diunpack" against each and every diskette image one at a time, and instead of having to automate it by writing a REXX script (which would probably be just as long), you can collate all of them into the following, single line command: Place the line below in a "batch file" a .cmd file of course. for %%1 in (*.?dk) do diunpack %%1 If you must use it at the commandline and NOT in a "batch file" then use only ONE percent sign instead of the double, as in:- for %1 in (*.?dk) do diunpack %1 Also, Go to:- http://xenia.sote.hu/~kadzsol/fixpak And download "prpfp.zip" or the complete url:- http://xenia.sote.hu/~kadzsol/fixpak/prpfp.zip "prpfp.zip" Enables you too automatically unpack all compressed files in a directory. Written by Zsolt Kadar of UpdCD fame (ie. Update CD). Quote on=== REXX script called PRPFP.CMD. To use this script UNPACK.EXE should be in the PATH. Example: PRPFP.CMD C:\fpk\todo Quote off=== This same UpdCD "Fixpack" web page above, has links to a lot of other usefull utilities and info as well. Hope this helps. Regards, BobT. On Mon, 02 Jul 2001 10:10:34 +0200, Kris Steenhaut wrote: > > >Trevor Clarke schreef: > >> Arh! >> >> Does anybody know how to extract dl_ files from a fixpack? This will save >> me a lot of stuffing around..... >> > >unpack olala.dl_ olala.dll > >or > >UNPACK A:olala.dl_ C:\OS2 > > >When unpack2 isn't in the path (as it should be), you'll have to specify the path >ofcoz. > > >Type help unpack at an os2 prompt to learn more about this little matter. > >-- >Groeten uit Gent, > > Kris > > ,-._|\ Robert Traynor (BobT) / Oz \ email rtraynoratnetstra dot com dot au \_,--.x/ 6============================================= From: "Paul Smedley" Date: Mon, 02 Jul 2001 20:04:27 +1100 Subject: [os2genau] Australian Tax Office eTax software Tried the eTax program from: ftp://etax.ato.gov.au/etax2001_1.exe and it installed perfectly, however, on loading the program, I get an error: Odin build: 20010701 debug Installed Odin: WarpIN Method of launching win32 apps: pe.exe OS/2 version: OS/2 Warp 4 Fixpack level: 15 Display driver + ver.: sdd beta 39 xf86sup.sys loaded: yes Windows dir: C:\ODIN System32 dir: C:\ODIN\SYSTEM32 Windows application: eTax 2001 - ftp://etax.ato.gov.au/etax2001_1.exe Problem description: Installs perfectly, but on program launch gives an error: "Win32 Error. Code 1004. Systemmessage, messageid = 0x00003ec." Clearing the error allows a new file to be started and a tax file number (9 digit number) to be entered, only to get an access violation: " Acces violation at address 004A9140 in module 'ETAX2001.EXE' Write of address 0000008." Log excerpt: t1: GetWindowRect 6800003e (515,406) (1539,1174) t1: CreateRectRegion (0,0)(1024,768) returned d1000014 t1: CreateRectRegion (0,0)(1024,768) returned d1000015 t1: CombineRgn d1000014 d1000014 d1000015 7 t1: GDI32: DeleteObject d1000015 t1: RedrawWindow 6800003e 0 d1000014 485 t1: GetRegionData d1000014 0 0 t1: GetRegionData d1000014 32 12f1e4 t1: WARNING: WinQueryUpdateRect 800002ea region 2000109 returned false even though we just invalidated part of a window!!! t1: GDI32: DeleteObject d1000014 t1: InvalidateRect 6800003e NULL erase=1 t1: RedrawWindow 6800003e 0 0 85 t1: USER32: SystemParametersInfoA uiAction: 48, uiParam: 0, pvParam: 1242964, fWinIni: 0 t1: USER32: SystemParametersInfoA 48, returned 1 t1: (FS=150B) ---[Exception Information]------------ t1: (FS=150B) Access Violation (hardware generated,portable,fatal) t1: (FS=150B) Read Access at address 00000008h t1: (FS=150B) Exception Address = 004117f7 t1: (FS=150B) Thread: Ordinal TID: 156, TID: 1, Priority: 0200h t1: (FS=150B) Process: PID: 83, Parent: 30, Status: 16 t1: (FS=150B) SS:ESP=0053:0012f8f0 EFLAGS=00012202 t1: (FS=150B) CS:EIP=005b:004117f7 EBP =0012f940 t1: (FS=150B) EAX=00000000 EBX=00000000 ESI=005bdc8c t1: (FS=150B) ECX=200728a4 EDX=200728a4 EDI=200728a4 t1: (FS=150B) DS=0053 ES=00000053 t1: (FS=150B) FS=0777 GS=0000 t1: (FS=150B) ---[End Of Exception Information]----- ** BEGIN STACK DUMP ** DOSCALL1.DLL 0004 at 0x1c04c168 ODINCRTD.DLL 0001 at 0x1d352488 DOSCALL1.DLL 0004 at 0x1c0401b5 PE.EXE 0001 at 0x00010f0c PE.EXE 0001 at 0x00010f41 between _cppinit + 5 and _setuparg - 3 PE.EXE 0001 at 0x00010ef3 between _exestart + 77 and __RunExitList - 19 ODINCRTD.DLL 0001 at 0x1d3321cd between _callback_opt_sys + 0x9 and _heapmin - 0x3 ETAX2001.EXE at 0x00530001 ETAX2001.EXE at 0x0047f400 ETAX2001.EXE at 0x0047f400 PE.EXE 0001 at 0x00010725 between main + 725 and AllocateExeMem__FPcPUl - 203 KERNEL32.DLL 0001 at 0x1d1d9a30 KERNEL32.DLL 0001 at 0x1d2105af between _CreateWin32PeLdrExeat24 + 0x3CF and __ct__13Win32PeLdrExeFPcUl - 0x3D KERNEL32.DLL 0001 at 0x1d1d9a30 ETAX2001.EXE at 0x005a8730 KERNEL32.DLL 0001 at 0x1d2039a6 between start__12Win32ExeBaseFv + 0xA6 and isDll__12Win32ExeBaseFv - 0x1E KERNEL32.DLL 0001 at 0x1d1e881e between _CallEntryPoint + 0x18 and EXC_push_frame__FP19_WINEXCEPTION_FRAME - 0x4 ETAX2001.EXE at 0x00403980 ETAX2001.EXE at 0x005a8799 ETAX2001.EXE at 0x004507a2 ETAX2001.EXE at 0x0045077e ETAX2001.EXE at 0x0045058b ETAX2001.EXE at 0x00450554 USER32.DLL 0001 at 0x14a1b9e4 between _DispatchMessageAat4 + 0x44 and _DispatchMessageWat4 - 0x8 PE.EXE 0001 at 0x000101e2 between main + 1E2 and AllocateExeMem__FPcPUl - 746 ETAX2001.EXE at 0x00530001 USER32.DLL 0001 at 0x14a1e580 between OSLibWinDispatchMsg__FP3MSGUl + 0x124 and OSLibWinGetMsg__FP3MSGUlUiT3T2 - 0x30 ETAX2001.EXE at 0x00530001 USER32.DLL 0001 at 0x14a1f007 between OSLibPostThreadMessage__FUlUiT2lT1 + 0xEB and HOOK_IsHooked__Fi - 0x12E1 USER32.DLL 0001 at 0x14a0200c PMMERGE.DLL 0004 at 0x1e934c3d USER32.DLL 0001 at 0x14a02177 between Win32WindowProc + 0x16B and Win32FrameWindowProc - 0xB91 USER32.DLL 0001 at 0x14a0ecfa between DispatchMsgA__15Win32BaseWindowFP3MSG + 0x26 and DispatchMsgW__15Win32BaseWindowFP3MSG - 0x6 USER32.DLL 0001 at 0x14a1152d between SendInternalMessageA__15Win32BaseWindowFUlUil + 0x259 and SendInternalMessageW__15Win32BaseWindowFUlUil - 0xAF USER32.DLL 0001 at 0x14a1e18f between _CallWindowProcAat20 + 0xEF and _CallWindowProcWat20 - 0x4D ETAX2001.EXE at 0x00447ea2 ETAX2001.EXE at 0x00435c74 ETAX2001.EXE at 0x00435c63 ETAX2001.EXE at 0x00435c4b KERNEL32.DLL 0001 at 0x1d1fa294 between _GetTEBFromThreadIdat4 + 0x5C and _GetTEBFromThreadHandleat4 - 0xC PE.EXE 0001 at 0x000100db between main + DB and AllocateExeMem__FPcPUl - 84D PE.EXE 0001 at 0x000100db between main + DB and AllocateExeMem__FPcPUl - 84D ETAX2001.EXE at 0x0044a967 KERNEL32.DLL 0001 at 0x1d1ed7d5 between leave__6VMutexFPUl + 0x18D and __ct__10VSemaphoreFiPUl - 0x73 KERNEL32.DLL 0001 at 0x1d1ed81f between leave__6VMutexFPUl + 0x1D7 and __ct__10VSemaphoreFiPUl - 0x29 KERNEL32.DLL 0001 at 0x1d1ed80f between leave__6VMutexFPUl + 0x1C7 and __ct__10VSemaphoreFiPUl - 0x39 KERNEL32.DLL 0001 at 0x1d1e7f70 between WriteLog + 0x2DC and WriteLogNoEOL - 0x10 ODINCRTD.DLL 0001 at 0x1d3493b4 ODINCRTD.DLL 0001 at 0x1d33b571 between _fprintfieee + 0x31 and _fprintf_ansi - 0xF ETAX2001.EXE at 0x0043604b ETAX2001.EXE at 0x00433588 ETAX2001.EXE at 0x0059a5a2 ETAX2001.EXE at 0x0059a181 ETAX2001.EXE at 0x005998c1 ETAX2001.EXE at 0x004117f7 ** END OF STACK DUMP ** Hope this helps - it'd be nice to do my tax without rebooting to Windows! Regards, Paul Smedley