Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Rick C. Hodgin

Pages: [1] 2 3
1
Hardware / Re: The best ThinkPad models for running ArcaOS?
« on: April 16, 2020, 03:31:37 am »
David, I have been trying to reach you.  Please email me.  Thank you.

2
Utilities / Re: Booting OS/2 with an Animation
« on: November 21, 2019, 12:50:38 pm »
Why you would want an animation, is beyond me. All it does is slow down booting. Even Microsoft doesn't do silly things like that.

Windows 7 has a boot up animation.  It plays in the foreground while Windows boots up in the background.  It was comprised of four window panes coalescing into a single window amid a light show.

Win 7 bootup animation

3
Applications / Re: XWP and folder file size listing
« on: November 18, 2019, 05:26:18 pm »
Use the mode command, something like
Code: [Select]
mode co80,100
will give you a hundred lines. The max that works is perhaps 103

Code: [Select]
mode 132,60
Instead of "co80" you can use a number to change the columns to a wider width as well.  I typically use 132,60 windows as this was the maximum native text-based resolution I could use on the old 3dfx V3 2000 graphics cards.  An excellent screen size for console needs.

4
Setup & Installation / Re: Trying to solve server crash
« on: November 15, 2019, 09:33:25 pm »
Hi,

I'm not trying to cause a big debate here, but just about 2 months ago I had to replace a bunch of failing capacitors on a 4 year old HP enterprise-grade sever.  I also just took some 5 year old HP desktop machines out of service which have capacitors showing signs of failure.

Poor quality capacitors are still a problem.

I'm surprised to hear that about HP.  I've purposefully chosen to buy HP equipment because the machines I've gotten from them have been rock solid stable.  I've had one laptop I used daily for 5+ years that my wife is still using daily.  It's almost 9 years old now.  I have another HP desktop machine that was purchased in 2007 that I use for development.  It is absolutely stable, and because of its design I was able to increase the memory to 8 GB and CPU to quad-core 2.4 GHz, and still have quite a decent performer out of it 12+ years later.

I would buy HP again in a heartbeat.  Never tried an enterprise-grade server, however. :-)

5
General Discussion / Re: Yahoo Groups End of Life
« on: November 08, 2019, 12:47:26 am »
You can find wget for OS/2 on (e.g.) Hobbes.  :)

wget 1.14 for OS/2 uploaded by Lewis Rosenthal.  Requires libc065.dll, gcc446.dll, tcpip32.dll.

Other versions

6
Programming / Re: Which debugger to use.
« on: November 07, 2019, 12:02:58 am »
I was wondering if masm386.exe is just masm.exe renamed?  MASM 6.x supported .486 and .586 in (at least in DOS).

I installed MASM 6.0b to c:\masm\binp and c:\masm\binb, and copied c:\masm\binb\masm.exe to c:\masm\binp\masm386.exe and ran nmake sd386.mk in the sd386src folder.  It worked!

I had to tweak a few of the assembly lines (a bug in MASM I assume, as that code is valid with an address override prefix byte):
Code: [Select]
; Did not work:
cmp byte ptr [di], 20h

; Changed to:
push edi
and edi,0ffffh
cmp byte ptr [edi], 20h
pop edi

And there were places like that in vbox.asm and putup.asm.

And it didn't recognize this in tcpip.c:
Code: [Select]
SOCECONNREFUSED
SOCEINTR
SOCENOTSOCK

I defined them all as -1 to see if it would compile and it did.  I'll find out their true values and update the code.

It also didn't find ilink.exe in the path, and it's not installed anywhere in my "dir /s ilink.exe" c:\ path.  I assume it's expecting a slightly newer version of icc than I have installed, and a version of MASM that includes the incremental linker.

7
Programming / Re: Which debugger to use.
« on: November 06, 2019, 12:11:53 pm »
My reading is that MASM 6 supported i386 (and I guess i486 etc) but did not support the flat memory model.

MASM 6 was given the .flat memory model support for OS/2 (as I understand it).  The .tiny memory model is also technically flat, but limited to 64KB.

Quote
Never used masm2alp or alp. Not really a programmer and about all I've done is porting assembly, mostly involving nasm. Simple stuff like the other day changing ".section rodate" to ".data" in some AS assembly (actually with ifdefs). The MASM386 code might just need some syntax fixes to port to another similar assembler and I do notice even going from MASM 5 to MASM 6 seems to take some work, at least going by the documentation.

I'll try it tonight.  I have MASM 6.0b.  Will start there.

8
Programming / Re: Which debugger to use.
« on: November 06, 2019, 04:52:56 am »
You may have to port the assembly to a different assembler, perhaps jwasm (fork of wasm, the Open Watcom assembler) which IIRC is fairly compatible to masm.

I was wondering if masm386.exe is just masm.exe renamed?  MASM 6.x supported .486 and .586 in (at least in DOS).

Have you used masm2alp?  And alp?

IBM's Assembly Language Processor might be interesting to look at.  I see it comes with VisualAge 4, as well as in several standalone forms.

I see also in my searching for masm386.exe that IBM's Macro Assembler back in 1987 included CodeView, and some of their ALP packages included a "cv.exe" as well (don't know if it was CodeView or not, but probably so based on file size).

9
Programming / Re: Which debugger to use.
« on: November 06, 2019, 04:34:03 am »
There's masm v6 and masm v5. As for masm386, it seems to have shipped with MS OS/2 ver2 and perhaps in some of the early v2 toolkits/sdks. Possibly the oldest NT one might run on OS/2 as well.
The current toolkit also contains masm2alp.exe which might work.

I still haven't been able to find masm386.exe.  I've tried IBM Macro Assembler from 1987 up thru Microsoft's Macro Assembler 6.0b.  They only have masm.exe.

10
Setup & Installation / Re: Screen Size
« on: November 06, 2019, 04:19:27 am »
Gradd only supports whatever the video bios supports. Panorama works around this by patching the bios to support wide screen monitors, based on the EDID, works fine here at 1680x1050 on real hardware.

Thank you.  I'll try that on my real 4.52 machine.

11
Setup & Installation / Screen Size
« on: November 05, 2019, 09:36:34 pm »
I've moved my Warp 4.52 machine to a 1680 x 1050 native monitor resolution.  I'm using VirtualBox's gradd driver and 1280 x 1024 integrates into the 1680 x 1050 when viewed in full screen.

How can I get it working natively at that resolution?
Is there a monitor table set up somewhere that I can edit to allow it to work an unusual resolution like 1680 x 1050?

13
Programming / Re: Which debugger to use.
« on: November 05, 2019, 12:22:43 pm »
Note I said MS OS/2 ver 2, a very rare beta that was never released as far as I know, not IBM OS/2 ver 2 which is what you likely have.

Yes.  Missed that. :-)

14
Programming / Re: Which debugger to use.
« on: November 05, 2019, 06:11:39 am »
There's masm v6 and masm v5. As for masm386, it seems to have shipped with MS OS/2 ver2 and perhaps in some of the early v2 toolkits/sdks.

Do you mean it shipped in the actual OS/2 retail box with the 3.5" floppies?

I have 2.0 ... and the floppy images for it.  I'll take a look tomorrow.  Thank you!

15
Programming / Re: Which debugger to use.
« on: November 05, 2019, 04:47:04 am »
That worked.  It's compiling all of the .C files.  It's looking for masm386 to compile the assembly.

I've never seen a masm386.exe program.  Microsoft's Macro Assembler 6.x had a masm.exe program that translated the old command line to the new one used by ml.exe.

Any idea where to find masm386?

In looking at the .asm files, they appear to be standard Microsoft Macro Assembler source code files.  It might be a 386-version of masm.exe that it's calling.

Anyone know where I can get an OS/2 version of Microsoft Macro Assembler?  I have a DOS-based version of 6.11D I bought back in the 90s.  I was able to copy it over, and it runs some of the binp\ files, but ml.exe only exists in the bin\ area, and it thinks it's a DOS program launching in a DOS shell, rather than OS/2 shell.

Pages: [1] 2 3