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 - Radek

Pages: 1 ... 8 9 [10] 11 12 ... 14
136
I am running eCS 1.1 in the original Virtual PC - not in the Micro$oft's one. And it works greatly. No special settings, 256 MB RAM, HD 2G, well, no sound, no USB, and S3 Trio video. The network works. I can communicate with the (real) PC using a network folder. All is installed on eXtreme Problems with SP2. I know that Warp would run as well, at least W4.
Whether you succeed with the original Virtual PC depends on PAE. You have 3G of memory so that the XP can have PAE set. If it is then you should be able to install VPC but you cannot run any virtual machines. If it is not set then you should pass.

137
Programming / Re: Problems with WinSetHook
« on: 2009.01.20, 10:21:24 »
Yes, it's the app which have been described in an EDM/2 article. The hook is used that way.

138
Programming / Re: Problems with WinSetHook
« on: 2009.01.19, 16:59:13 »
No, I don't have such contact. My only connection to the web is here from my work - and I cannot reach even netlabs.org because it uses XML and my micro$oft IE cannot process it.
At any rate, the problem will be with processing the hook entry during WinSetHook(). Perhaps something that was possible yesterday but what isn't possible today. One possible reason could be not shared DGROUP - OpenWatcom does not support shared DGROUP in DLLs. Even if the hook does not have any global data and it does everything on the stack (few bytes) and on the shared memory, the not shared DGROUP coud cause problems.
Okay, I can redo the hook in assembler but that's exactly what I wanted to avoid :)

139
Programming / Problems with WinSetHook
« on: 2009.01.19, 12:51:22 »
I have written a keyboard remapper. The remapper is simple, it monitors WM_CHAR messages (using a system-wide input hook) and manipulates them according to the custom keyboard layout. The remapper used to work perfectly - with RC2. The remapper crashes the operating system with RC4 and RC5.
Something has happened between RC2 and RC4. The question is what happened?
Here are some details about the remapper:
(1) It consists of a control EXE and a DLL containing the hook. The EXE and the DLL communicate using posted messages and a named shared memory.
(2) The EXE allocates the shared memory, fills in keyboard data, creates an object window, and sets the hook.
(3) The DLL monitors the WM_CHAR messages and it also posts its requests to the object window. Every time a WM_CHAR is passing, the DLL gets (DosGetNamedSharedMem) the shared memory and processes the message. Then it frees (DosFreeMem) the shared memory and returns.
(4) When the user decides to quit the remapper, the object window is closed, the hook and the shared memory are released and the application exits.
(5) The application is written in OpenWatcom.
All this worked flawlessly in RC2. In RC4, I get a system crash: some windows on the screen get whitened and I can see some hard disk activity, which I should not see. Luckily, Ctrl-Alt-Del works. The problem has been traced to WinSetHook(), that's this call which causes the crash. As a next step, I installed the hook locally (I added an entryfield for testing and installed the hook with HMQ_CURRENT). Now, the hook works again but the whole app is useless.
Therefore, the hook works as a local hook but it does not work as a system-wide hook. What can be wrong?

140
The usual reason is a missing DLL or a missing DLL entry. Not all winblows DLLs are in Win-OS/2. This can be fixed by getting the needed DLL. Also, not everything from DOS5 is emulated by OS/2 VDDs. This cannot be fixed so easily.

141
General Discussion / Re: A curious case of case.
« on: 2008.10.09, 09:52:32 »
IMO, it's not a bug, it's rather a "flexibility".
File names are case insensitive in OS/2. Therefore, 'mydir', 'MYDIR', and 'MyDir' are the same object. The operating system allows you to use all these names and it will follow your choice but all these names will always reference the same directory. It will also store your choice in system data tables on the HD so that when you create a 'SomeDir' directory, you will have 'SomeDir' and not 'SOMEDIR' but 'SOMEDIR' is equally good as 'SomeDir' for the operating system.
Therefore, always uppercase (or lowercase) all filenames before doing something with them (comparing, searching, sorting, and so on).

142
A few thoughts:
(1) 4 GB is the maximum which you can address with 32-bit addresses. AFAIK, eCS does not use PAE, so that 4 GB is the real maximum.
(2) The last valid physical address in your machine is 0FFFFFFFF. The (flat) segment size is this value plus one. If something attempts to add one to this value, the result will overflow and you get zero. This could be misinterpreted as "no memory present" among others.
(3) There is also "non system memory" (adapter RAM, adapter ROM, etc.) in your machine, which must be mapped somewhere. But where? All available addresses are already occupied by your RAM. This can be another source of fatal conflicts.
Summarizing the thoughts: Something gets confused by your 4 GB of RAM. IMO, you see the "OS/2 box" until the loader tries to build page tables and to switch to protected mode. Then the loader crashes and pulls the emergency brake. IMO, 4 GB or RAM isn't a good idea as long as eCS is concerned.
I can be completely wrong. I have 2 GB and I've never tried 4 GB.

143
Setup & Installation / Re: Installation won't fix disk
« on: 2008.09.09, 17:56:32 »
Saijin, XP doesn't need to disable BM but it does it so that you won't get BM screen during XP installation. But this is not the problem. If XP simply disabled BM and told you how to get it back after installation, so be it. But XP renders BM unusable. You cannot get it back because XP has fouled OS/2 partitions in the meantime.
I don't know whether Linux or BeOS does the same stupid thing. I have written about my own experience with installing eCS and winblows 2000 on the same HD. It is possible but you need to prevent winblows from attacking other partitions, therefore, install winblows first and eCS then. If you start with eCS then you get problems.

144
Setup & Installation / Re: Installation won't fix disk
« on: 2008.09.09, 09:38:15 »
What the f...!!!?? Winblows, what else. It is known that XP (in fact, all Neanderthal Technology versions of winblows) modifies partitions which it was not asked to touch. This concers winblows installation (you say: "install here" and XP will foul all partitions it finds around) and also wnblows HD manager. Results:
- you lose boot manager (winblows has wiped it out)
- when you reinstall BM, then winblows will not work, eCS will not work or nothing will work at all.
The only way out is DFSee. Forcing the partitions back does not suffice, you have to fix the partitions first.

145
Hardware / Re: What laser printer?
« on: 2008.09.04, 16:21:10 »
LJ 1200 - supported by eCS, works perfectly. At present, this printer must be rather cheap. I have one and I have no complaints with it.

146
Vista = XP + Digital Restriction Management + Treacherous Computing Platform. The "bonus pack", which "extends" XP to Vista is nothing to be keen on  >:(  More about Vista and why people don't like it, see http://badvista.fsf.org

147
Setup & Installation / Re: Lenovo M57 & USB Support
« on: 2008.08.13, 10:56:27 »
Minor notes
(a) The /REQ parameter. One cause of problems can be /REQ:USBOHCD$ because you aren't loading any USBOHCD.SYS drivers. USBD.SYS will try to get USBOHCD$ IDC entry point and it gets none. If you want the /REQ parameter then remove the USBOHCD$ specification.
(b) A mismatch between USB drivers an USB devices should not cause a Chernobyl screen. It will cause non-functionality of some USB devices. Note that you cannot add more than 4 drivers for each USB specification during installation (this was true for eCS 2.0 RC1, I am not sure whether it is true now) so that you can get non-functional USB devices during install. This will be fixed later, after installation.
My own experience (6 UHCI, 2 EHCI) - mouse does not work after PM shell startup. The mouse gets alive and kicking after updating CONFIG.SYS and rebooting.
(c) A very good USB information and configuration utility: see Hobbes, usbcfg7a.zip

148
Article Discussions / Re: Papyrus 2008 (DEMO)
« on: 2008.08.12, 09:20:22 »
eCS 2.0 RC1 (because I cannot install eCS on my NB, I am upgrading in longer periods). No nonstandard DOSCALL1 unless eCS itself made it nonstandard.

149
Article Discussions / Re: Papyrus 2008 (DEMO)
« on: 2008.08.11, 09:39:46 »
I have tried the german version of new Papyrus. It started only once, then I got GP faults (DOSCALL1, NULL pointer dereference) on every next start. Next possible start of Papyrus only after complete reinstalling. Is that intentional? If it is then I was correct when I throwed Papyrus into trash can.

150
Setup & Installation / Re: install warp 4 with windows xp
« on: 2008.08.08, 11:37:14 »
Step by step directions - (a) if you can start from an empty HD (without already having XP on the disk) and if the directions will work for XP  ;D  I have installed winblows 2003 and eCS on the same HD. Let us hope that if it worked for winblows 2003, it will work for XP as well.
(1) Delete all pratitions from the HD. Winblows pratitions do not create a correct partition info in MBR. Result: the eCS FDISK will refuse cooperating if it finds such partitions on your HD. Deleting the partitons could be a problem - again, bad MBR info. Tested ways: (a) DOS5 FDISK form diskette and (b) Winblows 98 CD. Start winblows 98 from the CD. If will fail immediately because it will not recognize your hardware but you will end on the promt with access to your CD. Start FDISK from the root of your CD and it is able to to wipe out the partitions with bad MBR info as well.
(2) Start from eCS CD and create a partition for your XP. Make the partition installable and startable so that FDISK will not complain when you quit it. Switch to XP CD, quit FDISK and reboot (by means of ctrl-alt-del, we need a partition with correct MBR info, we are not about to continue installation of eCS).
Now you have a single partition on your HD prepared for your XP. The fact that the partition is the only one on your HD is important: XP fouls partitions which it was not said to touch. You command XP "install here", and XP will write on other partitions as well  :-\  If you have installed something on these partitions, you are losing it. Now, XP cannot do that, there is only one partition on your HD.
(3) Install XP. Tell XP to install on the partition created in (2). Install service packs (I don't know whether you need them but winblows 2003 needed SP3 or so - otherwise, winblows wiped out boot manager or network didn't work).
(4) Back to eCS. Boot from eCS CD. The MBR info is now okay so that you will pass through FDISK. Create a boot manager partition, create a system partition for eCS, install boot manager, add both XP and the eCS partition to the boot manager menu (all this is done from FDISK). Format, install.
(5) Do all partition management from eCS. After having installed, create data partitions both for XP and eCS. Next time you will start XP, format data partitions for XP (seems to be safe). At any rate, forget XP hard disk manager! Otherwise, you are risking that XP will foul your partitions again!
(6) Now, you have (you should have) boot manager and both XP and eCS in it. Both the operating system and XP should start.

Pages: 1 ... 8 9 [10] 11 12 ... 14