|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| I'm trying to get the PocketC runtime to work on this x86 CE5 device, however it requires IMDECMP.DLL which was apparently removed after CE4. Any ideas perhaps as to how I could acquire a CE4 x86 IMDECMP.DLL?  |
|
| |
|
Subscribers H/PC Guru Posts: | 5,278 |
Location: | United States | Status: | |
| Can you try looking for this WYSE model CE4 thin client's ROM image?
Wyse Winterm Thin Client WT3235LE 902024-01 WINDOWS CE. NET 4.1
I tried looking too but no luck yet |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| |
|
| |
|
Administrator H/PC Oracle Posts: | 17,720 |
Location: | United Kingdom | Status: | |
| According to https://www.dell.com/support/contents/en-uk/article/product-support/... you were supposed to be able to translate the serial number into a Dell service tag. However using the serial number off of it does not seem to work with products of this age and Dell doesn't have the model listed in their support list. |
|
| |
|
Subscribers H/PC Guru Posts: | 5,278 |
Location: | United States | Status: | |
| I think this thin client ram ce 4.2
Try searching
HP Compaq t5500 Thin Client Microsoft Windows CE .NET 4.2 Image driver v.4.22.144 |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| Quote torch - 2022-11-29 3:54 PM
I think this thin client ram ce 4.2
Try searching
HP Compaq t5500 Thin Client Microsoft Windows CE .NET 4.2 Image driver v.4.22.144
Oh my gosh, found it!  |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| Renaming the flash.img file to flash.ibr allows me to open it with 7zip, but we're back to the issue of not being able to extract any of the files, just to view them |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| I tried running the tool on an XP machine (using the -xb switch to avoid it checking if it's actually being run on an HP machine), but it just gives me the disk geometry error. I got the same error a while ago when trying to flash to a USB drive on an actual HP thin client. |
|
| |
|
Subscribers H/PC Guru Posts: | 5,278 |
Location: | United States | Status: | |
| Ok. Do me a favor.
Link me both images for 4.2 and 5.0 and remind me of the flag to disregard the model check (I think -xb)?
I’ll try:
Installing them both
But:
I’m going to use a Debian live usb this time to dump the drive instead. Maybe I’ll be able to give you more files as opposed to the DOS line |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| Quote torch - 2022-11-29 4:46 PM
Ok. Do me a favor.
Link me both images for 4.2 and 5.0 and remind me of the flag to disregard the model check (I think -xb)?
I’ll try:
Installing them both
But:
I’m going to use a Debian live usb this time to dump the drive instead. Maybe I’ll be able to give you more files as opposed to the DOS line
Awesome!! Really hope it works out with Linux this time. For the t5500 I was only able to find a 4.2 image (click the green download button at the top ), but I found a 5.0 image for the t5520!
The switch is -xb, correct! |
|
| |
|
Subscribers H/PC Guru Posts: | 5,278 |
Location: | United States | Status: | |
| I tried:
-Flashing the CE4.2 image. Same thing, just splash screen but doesn't finish booting
-Live USB for Debian 8 and Debian 11 (none seem to support the funky gfx card)
But:
I got to thinking when I was using the directory structure in CE6.0..
What if that .nbr file is just loaded upon boot as a ramdisk? That would make sense because programs I install don't persist after reboot. That would also make sense why the C: drive just has those silly cab files that we saw from the 5.0 image I sent you.
So the .nbr file is never really "extracted" until it's booted as that ramdisk.
I don't think Linux would show us more than what I sent you...
Unless you had another idea? |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| Quote torch - 2022-11-30 6:52 AM
I tried:
-Flashing the CE4.2 image. Same thing, just splash screen but doesn't finish booting
-Live USB for Debian 8 and Debian 11 (none seem to support the funky gfx card)
But:
I got to thinking when I was using the directory structure in CE6.0..
What if that .nbr file is just loaded upon boot as a ramdisk? That would make sense because programs I install don't persist after reboot. That would also make sense why the C: drive just has those silly cab files that we saw from the 5.0 image I sent you.
So the .nbr file is never really "extracted" until it's booted as that ramdisk.
I don't think Linux would show us more than what I sent you...
Unless you had another idea?
Do you mean the .ibr file? That's the disk image that gets applied to the internal flash memory. The nk.bin file within is absolutely loaded into RAM upon boot, it's so strange to me that it seems to have vanished entirely  None of my PC based CE systems have that, they all have their nk.bin visible |
|
| |
|
Subscribers H/PC Guru Posts: | 5,278 |
Location: | United States | Status: | |
| Slightly offtopic, have you found coredll.dll & mfcce300.dll for x86? I compiled some PocketPC progs for x86 so I wanted to try to get running |
|
| |
|
Subscribers H/PC Guru Posts: | 5,278 |
Location: | United States | Status: | |
| Hey! eVC 3 (and probably 4) have a .lib file for that dll you wanted FOR X86!!!
I just need help - I don't know how to compile a lib file to a dll |
|
| |
|
Administrator H/PC Oracle Posts: | 17,720 |
Location: | United Kingdom | Status: | |
| You can't convert a lib to a dll, it's a definition file for the dll, not the source code. |
|
| |
