Compaq LTE Elite 4/50E - Revision history

Peetz0r: Floppy emulator

2024-08-13T09:57:13Z

Floppy emulator

← Older revision		Revision as of 09:57, 13 August 2024
Line 39:		Line 39:

	The floppy drive does not work. It does make some noises but the disk never spins. The rubber belt inside was very much disintegrating, but replacing the belt did not result in a working drive yet. But even if it did, I have no other devices anywhere with a floppy drive anyway. WONTFIX. By the way, the drive is a Citizen W1D.		The floppy drive does not work. It does make some noises but the disk never spins. The rubber belt inside was very much disintegrating, but replacing the belt did not result in a working drive yet. But even if it did, I have no other devices anywhere with a floppy drive anyway. WONTFIX. By the way, the drive is a Citizen W1D.

			2024 update: I fixed it. See [[Compaq_LTE_Elite_4/50E#Floppy_emulator]]

	== Display ==		== Display ==
Line 132:		Line 134:

	Also, let's not [https://www.youtube.com/watch?v=BX8rJtpTTVk do what AkBKukU did].		Also, let's not [https://www.youtube.com/watch?v=BX8rJtpTTVk do what AkBKukU did].

			== Floppy emulator ==

			Someone made a floppy drive emulator for it!
			* Video: https://www.youtube.com/watch?v=6x54SSQnMsc
			* Github repo: https://github.com/silvervest/OpenFlops-W1D
			* Store: https://silvestrons-bits-and-bytes.square.site/product/openflops-w1d-floppy-drive-emulator/6

	= Software =		= Software =

Peetz0r: /* New Battery? */

2019-09-12T07:29:02Z

New Battery?

← Older revision		Revision as of 07:29, 12 September 2019
Line 98:		Line 98:
	[https://github.com/volkertb/temu-vsb SBEMU and TEMU] are old 1990's era drivers to partially emulate Sound Blaster or Tandy sound on the Covox Speech Thing. This depends on QEMM and does not work with EMM386. I haven't tried with QEMM yet.		[https://github.com/volkertb/temu-vsb SBEMU and TEMU] are old 1990's era drivers to partially emulate Sound Blaster or Tandy sound on the Covox Speech Thing. This depends on QEMM and does not work with EMM386. I haven't tried with QEMM yet.

	== New Battery? ==		== New Battery? (obsolete) ==
	[[File:Compaq_LTE_4-50E_powerbang_2.JPG\|240px\|thumb\|right\|Powerbang installed in the bay, on the left there a pi0w]]		[[File:Compaq_LTE_4-50E_powerbang_2.JPG\|240px\|thumb\|right\|Powerbang installed in the bay, on the left there was a pi0w]]

	I have decided to replace the original battery with a modern version, based on the [[User:Mux\|Muxtronics Powerbang]] with 3 18650 cells. This would be more than the capacity of the original battery in less than 1/3rd of the volume in cells. I can charge it using a micro usb port on the front. The Powerbang is programmable and does pretty accurate measurements.		I have decided to replace the original battery with a modern version, based on the [[User:Mux\|Muxtronics Powerbang]] with 3 18650 cells. This would be more than the capacity of the original battery in less than 1/3rd of the volume in cells. I can charge it using a micro usb port on the front. The Powerbang is programmable and does pretty accurate measurements.
Line 109:		Line 109:
	* maybe add a led battery indicator on the front		* maybe add a led battery indicator on the front
	* improve usability of the front panel, maybe by making it thinner, and making the shape more like the laptop itself and less like a flat surface		* improve usability of the front panel, maybe by making it thinner, and making the shape more like the laptop itself and less like a flat surface

			== No Battery! ==
			[[File:Compaq_LTE_4-50E_usb-pd_1.jpg\|240px\|thumb\|left\|USB PD module installed in the bay, on the left there's a GL.iNet]]
			[[File:Compaq_LTE_4-50E_usb-pd-2.jpg\|240px\|thumb\|left\|It works! (if your USB PD source can supply 12V that is...)]]
			Over a year later, after doing [https://gitlab.com/Peetz0r/usb-c-grok some] [[PeetR0ver\|other]] [[Monsteraccu\|projects]] involving USB type C and USB Power Delivery, I decided that this project needed to join the bunch. Also having another battery to keep charged in a project that is infrequently used is not ideal.

			So I basically re-3d-modeled the battery bay replacement to have a small USB PD trigger module in the front. This also leaves enough space to have the GL.iNet in the front panel too (I got rid of the pi0w, it was unreliable as fuck). Also printed it on the Prusa in 2 colors because why not (all early 2018 printing was done on the Ultimaker).

	== Memory upgrade ==		== Memory upgrade ==

Peetz0r: /* CVX4 */

2018-09-11T12:41:00Z

CVX4

← Older revision		Revision as of 12:41, 11 September 2018
Line 94:		Line 94:

	=== CVX4 ===		=== CVX4 ===
	This is basically a Covox Speech Thing clone, but less ugly. The output is a pure line ~~leven~~ signal. It won't drive headphones and really needs an amplifier. But it works. There are even Windows 3.11 drivers for it.		This is basically a Covox Speech Thing clone, but less ugly. The output is a pure line level signal. It won't drive headphones and really needs an amplifier. But it works great when hooked up to the TV at the space. There are even Windows 3.11 drivers for it.

	[https://github.com/volkertb/temu-vsb SBEMU and TEMU] are old 1990's era drivers to partially emulate Sound Blaster or Tandy sound on the Covox Speech Thing. This depends on QEMM and does not work with EMM386. I haven't tried with QEMM yet.		[https://github.com/volkertb/temu-vsb SBEMU and TEMU] are old 1990's era drivers to partially emulate Sound Blaster or Tandy sound on the Covox Speech Thing. This depends on QEMM and does not work with EMM386. I haven't tried with QEMM yet.

Peetz0r at 07:48, 12 May 2018

2018-05-12T07:48:14Z

← Older revision		Revision as of 07:48, 12 May 2018
Line 55:		Line 55:

	== Serial port ==		== Serial port ==
	I also ordered a bunch of [https://www.aliexpress.com/item/1pcs-lot-MAX3232-RS232-to-TTL-Serial-Port-Converter-Module-DB9-Connector-MAX232/32722395554.html ~~MAX232~~ boards] and I had some CH340 ttl-serial-usb lying around. So I took one of both and connected them to my modern linux laptop at first. I could get a serial console, run ssh, and even revbank inside the Windows 3.1 Terminal app.		I also ordered a bunch of [https://www.aliexpress.com/item/1pcs-lot-MAX3232-RS232-to-TTL-Serial-Port-Converter-Module-DB9-Connector-MAX232/32722395554.html MAX3232 boards] and I had some CH340 ttl-serial-usb lying around. So I took one of both and connected them to my modern linux laptop at first. I could get a serial console, run ssh, and even revbank inside the Windows 3.1 Terminal app.

	So I now needed a way to connect the Badge sitting in the battery bay to the serial port on the back of the laptop. Complete disassembly was required. I decided to make a second serial port parallel to the first port. This breaks when you connect devices to both ports, [http://www.jargon.net/jargonfile/d/Dontdothatthen.html so don't do that then!]. At first I connected it directly to a ~~MAX232~~ board, but than I decided to make it removable, just like the original battery. So I yanked a DE9 port from an old desktop board from the e-waste pile and soldered it in parallel to the rear port on a short ribbon cable, snipped away some plastic, added some padding and hotglue. We now have a internal DE9 serial port inside the <del>battery bay</del> BadgeBay™!		So I now needed a way to connect the Badge sitting in the battery bay to the serial port on the back of the laptop. Complete disassembly was required. I decided to make a second serial port parallel to the first port. This breaks when you connect devices to both ports, [http://www.jargon.net/jargonfile/d/Dontdothatthen.html so don't do that then!]. At first I connected it directly to a MAX3232 board, but than I decided to make it removable, just like the original battery. So I yanked a DE9 port from an old desktop board from the e-waste pile and soldered it in parallel to the rear port on a short ribbon cable, snipped away some plastic, added some padding and hotglue. We now have a internal DE9 serial port inside the <del>battery bay</del> BadgeBay™!

			I only found out that the boards have a MAX3232 (not a MAX232) on board, which is a good thing. The MAX232 can only be powered from 5V and can only produce 5V out (the input is 3.3V tolerant). But the MAX3232 can be powered anywhere between 3.0V and 5.5V, and the logic output voltage will be that voltage as well. So, the MAX3232 is just a more flexible version of the MAX232.

	During the disassembly process the fan connector broke off. But that's okay as you'll read in the next section.		During the disassembly process the fan connector broke off. But that's okay as you'll read in the next section.
Line 63:		Line 65:
	== +5V hackery ==		== +5V hackery ==

	Up to this part, the Badge and the ~~MAX232~~ were powered from an external USB supply (mostly my modern laptop since I was flashing/debugging the Badge all the time anyway). But this wouldn't be good enough for a permanent setup. So I needed a way to connect Ground and +5V from the laptop to the badge. Ground was already present in the DE9 connector, so we are already halfway! But that's not enough. I needed a way to connect one extra pin reliably while keeping the carefully constructed hotpluggable toolless BadgeBay™ system intact. So i snipped one of the retaining screw thingies seperate from the shielding, connected a red wire, and then I hotglued a metal spring to the inside of the laptop. I soldered a red wire to the spring as well. I lined the spring up with the DE9 retaining screw.		Up to this part, the Badge and the MAX3232 were powered from an external USB supply (mostly my modern laptop since I was flashing/debugging the Badge all the time anyway). But this wouldn't be good enough for a permanent setup. So I needed a way to connect Ground and +5V from the laptop to the badge. Ground was already present in the DE9 connector, so we are already halfway! But that's not enough. I needed a way to connect one extra pin reliably while keeping the carefully constructed hotpluggable toolless BadgeBay™ system intact. So i snipped one of the retaining screw thingies seperate from the shielding, connected a red wire, and then I hotglued a metal spring to the inside of the laptop. I soldered a red wire to the spring as well. I lined the spring up with the DE9 retaining screw.

	Back to the broken fan connector. I spliced the wires from there and from the spring (and later another wire for the OPL2LPT) together and connected those to the pads behind the fan connector. We now have a BadgeBay™ +5V rail!		Back to the broken fan connector. I spliced the wires from there and from the spring (and later another wire for the OPL2LPT) together and connected those to the pads behind the fan connector. We now have a BadgeBay™ +5V rail!
Line 71:		Line 73:
	<gallery>		<gallery>
	Compaq LTE 4-50E battery-caddy-print-1.JPG\|One of the failed BadgeBay™ designs. The Hexagon grid on the bottom layer was too thin.		Compaq LTE 4-50E battery-caddy-print-1.JPG\|One of the failed BadgeBay™ designs. The Hexagon grid on the bottom layer was too thin.
	Compaq LTE 4-50E usb-serieel.jpg\|Serial - ~~MAX232~~ board - CH340 board - USB.		Compaq LTE 4-50E usb-serieel.jpg\|Serial - MAX3232 board - CH340 board - USB.
	Compaq LTE 4-50E revbank.jpg\|Revbank over serial console.		Compaq LTE 4-50E revbank.jpg\|Revbank over serial console.
	Compaq LTE 4-50E internal-serial-0.JPG\|Bottomside of the mainboard.		Compaq LTE 4-50E internal-serial-0.JPG\|Bottomside of the mainboard.
Line 97:		Line 99:

	== New Battery? ==		== New Battery? ==
	[[File:Compaq_LTE_4-~~50E_powerbang_1~~.JPG\|240px\|thumb\|right\|Powerbang installed in the bay, on the left there ~~is room for~~ a pi0w]]		[[File:Compaq_LTE_4-50E_powerbang_2.JPG\|240px\|thumb\|right\|Powerbang installed in the bay, on the left there a pi0w]]

	I have decided to replace the original battery with a modern version, based on the [[User:Mux\|Muxtronics Powerbang]] with 3 18650 cells. This would be more than the capacity of the original battery in less than 1/3rd of the volume in cells. I can charge it using a micro usb port on the front. The Powerbang is programmable and does pretty accurate measurements.		I have decided to replace the original battery with a modern version, based on the [[User:Mux\|Muxtronics Powerbang]] with 3 18650 cells. This would be more than the capacity of the original battery in less than 1/3rd of the volume in cells. I can charge it using a micro usb port on the front. The Powerbang is programmable and does pretty accurate measurements.
Line 233:		Line 235:

	== PPPoS, GL.iNet, SHA2017 badge and Pi0w ==		== PPPoS, GL.iNet, SHA2017 badge and Pi0w ==
	[[File:~~Compaq_LTE_4~~-~~50E_inside~~.JPG\|240px\|thumb\|right\|~~GL.iNet inside!~~]]		[[File:Compaq LTE 4-50E_powerbang_3.JPG\|240px\|thumb\|right\|pi0w with large 470µF cap connected to MAX3232 module]]
	I have three different PPP clients on the laptop right now. DOSPPP and Trumpet Winsock and pppd on BasicLinux. All of them work with pppd in OpenWRT on the [[GL-iNet]], after much fiddling around with settings and scripts everywhere. But there is one problem. The GL.iNet is way too powerful with 8x more RAM and CPU clockspeed. It's just... ''wrong''. So I decided to try the SHA2017 as my PPP-UART device.		I have three different PPP clients on the laptop right now. DOSPPP and Trumpet Winsock and pppd on BasicLinux. All of them work with pppd in OpenWRT on the [[GL-iNet]], after much fiddling around with settings and scripts everywhere. But there is one problem. The GL.iNet is way too powerful with 8x more RAM and CPU clockspeed. It's just... ''wrong''. So I decided to try the SHA2017 as my PPP-UART device.

Line 240:		Line 242:
	I can ping from Trumpet to the Badge, and from the Badge to the rest of the network, but not all the way in one go. ARP proxying is really needed. But it's unavailable in the code [https://github.com/espressif/esp-idf/blob/master/components/lwip/netif/ppp/ppp.c#L1052 right here] and in other places.		I can ping from Trumpet to the Badge, and from the Badge to the rest of the network, but not all the way in one go. ARP proxying is really needed. But it's unavailable in the code [https://github.com/espressif/esp-idf/blob/master/components/lwip/netif/ppp/ppp.c#L1052 right here] and in other places.

	The latest iteration of the wifi adapter is based on the Raspberry Pi Zero W (hereafter: pi0w), because it is smaller than a GL.iNet. This leaves room to build a new battery in the same bay. I ~~think~~ I ~~still have a~~ microSD card ~~somewhere~~, ~~now just lemme find~~ it...		The latest iteration of the wifi adapter is based on the Raspberry Pi Zero W (hereafter: pi0w), because it is smaller than a GL.iNet. This leaves room to build a new battery in the same bay. I used a brand new high-end UHS-I 16GB microSD card because that was the only thing I could find. Overkill, but hey. I had to add a big cap to make the 5V stable enough for the pi0w to not randomly reboot or loose wifi. Strange, since the GL.iNet and Badge did not have any issues with the exact same supply.

			The Pi actually generates the 3.3V to power the MAX3232 so it can output 3.3V signals and not kill the Pi, which could have happened if I left it powered directly from 5V as it was before with the GL.iNet.

	This basically means than I have decided not to try using the Badge anymore. I might still try other esp32 (or even esp8266) solutions in the future, many boards are small enough to fit in the same place.		This basically means than I have decided not to try using the Badge anymore. I might still try other esp32 (or even esp8266) solutions in the future, many boards are small enough to fit in the same place.

Peetz0r at 21:58, 3 May 2018

2018-05-03T21:58:31Z

← Older revision		Revision as of 21:58, 3 May 2018
Line 97:		Line 97:

	== New Battery? ==		== New Battery? ==
			[[File:Compaq_LTE_4-50E_powerbang_1.JPG\|240px\|thumb\|right\|Powerbang installed in the bay, on the left there is room for a pi0w]]

	I have decided to replace the original battery with a modern version, based on the [[User:Mux\|Muxtronics Powerbang]] with 3 18650 cells. This would be more than the capacity of the original battery in less than 1/3rd of the volume in cells. I can charge it using a micro usb port on the front. The Powerbang is programmable and does pretty accurate measurements.		I have decided to replace the original battery with a modern version, based on the [[User:Mux\|Muxtronics Powerbang]] with 3 18650 cells. This would be more than the capacity of the original battery in less than 1/3rd of the volume in cells. I can charge it using a micro usb port on the front. The Powerbang is programmable and does pretty accurate measurements.

Peetz0r: /* New Battery? */

2018-05-03T21:54:55Z

New Battery?

← Older revision		Revision as of 21:54, 3 May 2018
Line 98:		Line 98:
	== New Battery? ==		== New Battery? ==

	~~It might be possible to build a new rechargable battery for this machine. If~~ I ~~decide~~ to ~~use something more compact than~~ the ~~badge (like~~, ~~any normal esp32 or esp8266 module, or a GL-iNet~~ with ~~the case stripped off), that would leave room for at least~~ 3 ~~or possibly 6~~ 18650 ~~<del>Ni-MH</del> Li-Ion~~ cells. ~~The~~ original battery ~~had a capacity~~ of ~~24 Wh~~ in 10 cells. ~~3 modern cells would already be more~~.		I have decided to replace the original battery with a modern version, based on the [[User:Mux\|Muxtronics Powerbang]] with 3 18650 cells. This would be more than the capacity of the original battery in less than 1/3rd of the volume in cells. I can charge it using a micro usb port on the front. The Powerbang is programmable and does pretty accurate measurements.

	~~Connecting it to~~ the ~~original connector would be... interesting, since it would probably try to charge it at a unsuitable voltage. So it might be smart to protect the pack output to let it only discharge trough~~ the ~~old connector,~~ and ~~to create a seperate charger/BMS~~ with ~~a seperate~~, ~~new, charge port. This could be micro~~-usb on the ~~front side.~~		Plans for the future:
			* communicate between the pi0w and powerbang over serial (not interfering with pppos, requires either softserial or serial-usb over the OTG port)
	~~This~~ might be ~~based~~ on the ~~[[User:Mux\|Muxtronics Powerbang]]~~, ~~because of reasons.~~		* make a web interface to monitor power usage, compatible with ancient browsers
			* upgrade to the USB-C PD version which mux might be working on
			* maybe add a led battery indicator on the front
			* improve usability of the front panel, maybe by making it thinner, and making the shape more like the laptop itself and less like a flat surface

	== Memory upgrade ==		== Memory upgrade ==

Peetz0r at 21:30, 3 May 2018

2018-05-03T21:30:38Z

← Older revision		Revision as of 21:30, 3 May 2018
Line 228:		Line 228:
	It runs very slow in default multi user, but it's reasonably fast in single user mode. So yeah, let's do everything as root all the time! I wrote my own startup script as a ghetto replacement for rc.		It runs very slow in default multi user, but it's reasonably fast in single user mode. So yeah, let's do everything as root all the time! I wrote my own startup script as a ghetto replacement for rc.

	== PPPoS, GL.iNet ~~and~~ SHA2017 badge ==		== PPPoS, GL.iNet, SHA2017 badge and Pi0w ==
	[[File:Compaq_LTE_4-50E_inside.JPG\|240px\|thumb\|right\|GL.iNet inside!]]		[[File:Compaq_LTE_4-50E_inside.JPG\|240px\|thumb\|right\|GL.iNet inside!]]
	I have three different PPP clients on the laptop right now. DOSPPP and Trumpet Winsock and pppd on BasicLinux. All of them work with pppd in OpenWRT on the [[GL-iNet]], after much fiddling around with settings and scripts everywhere. But there is one problem. The GL.iNet is way too powerful with 8x more RAM and CPU clockspeed. It's just... ''wrong''. So I decided to try the SHA2017 as my PPP-UART device.		I have three different PPP clients on the laptop right now. DOSPPP and Trumpet Winsock and pppd on BasicLinux. All of them work with pppd in OpenWRT on the [[GL-iNet]], after much fiddling around with settings and scripts everywhere. But there is one problem. The GL.iNet is way too powerful with 8x more RAM and CPU clockspeed. It's just... ''wrong''. So I decided to try the SHA2017 as my PPP-UART device.
Line 235:		Line 235:

	I can ping from Trumpet to the Badge, and from the Badge to the rest of the network, but not all the way in one go. ARP proxying is really needed. But it's unavailable in the code [https://github.com/espressif/esp-idf/blob/master/components/lwip/netif/ppp/ppp.c#L1052 right here] and in other places.		I can ping from Trumpet to the Badge, and from the Badge to the rest of the network, but not all the way in one go. ARP proxying is really needed. But it's unavailable in the code [https://github.com/espressif/esp-idf/blob/master/components/lwip/netif/ppp/ppp.c#L1052 right here] and in other places.

			The latest iteration of the wifi adapter is based on the Raspberry Pi Zero W (hereafter: pi0w), because it is smaller than a GL.iNet. This leaves room to build a new battery in the same bay. I think I still have a microSD card somewhere, now just lemme find it...

			This basically means than I have decided not to try using the Badge anymore. I might still try other esp32 (or even esp8266) solutions in the future, many boards are small enough to fit in the same place.

Peetz0r at 21:26, 3 May 2018

2018-05-03T21:26:22Z

← Older revision		Revision as of 21:26, 3 May 2018
Line 11:		Line 11:

	== Status when I found it ==		== Status when I found it ==
	It had the (presumably) original harddrive still present and working (after 23 years!). On it was Windows 3.x with lots of Compaq bloatware and personal data of the previous owner. I decided ~~top~~ keep this as-is, because the original software/drivers/etc is hard to find/replace but I did not peek around very much because of privacy reasons. The battery was very much dead, the floppy drive did not work, and the bottom RAM cover was missing, but it did work just fine.		It had the (presumably) original harddrive still present and working (after 23 years!). On it was Windows 3.x with lots of Compaq bloatware and personal data of the previous owner. I decided to keep this as-is, because the original software/drivers/etc is hard to find/replace but I did not peek around very much because of privacy reasons. The battery was very much dead, the floppy drive did not work, and the bottom RAM cover was missing, but it did work just fine.

	A service manual was easy to find online: [[Media:Compaq LTE Elite service manual.pdf]] (2.6 MB, 387 pages).		A service manual was easy to find online: [[Media:Compaq LTE Elite service manual.pdf]] (2.6 MB, 387 pages).

Peetz0r: /* +5V hackery */

2018-04-19T03:01:47Z

+5V hackery

← Older revision		Revision as of 03:01, 19 April 2018
Line 67:		Line 67:
	Back to the broken fan connector. I spliced the wires from there and from the spring (and later another wire for the OPL2LPT) together and connected those to the pads behind the fan connector. We now have a BadgeBay™ +5V rail!		Back to the broken fan connector. I spliced the wires from there and from the spring (and later another wire for the OPL2LPT) together and connected those to the pads behind the fan connector. We now have a BadgeBay™ +5V rail!

	At this point the BadgeBay™ hardware was more or less working. A few weeks later I ordered my soundcards. The CVX4 does not need any external power, but the OPL2LPT does. It has a mini-usb connector to power it from a nearby USB port, which this laptop lacks. Powering it from any external source works fine but is clunky. The OPL2LPT kit already has pads for a DIY power header. Since the ground was already connected trough the pins in the port and/or shielding, I again only needed to worry about the +5V. So I added another red wire to my already existing splice near the fan connector and made this one long enough to reach all the way from there to the left side of the laptop, trough the PCMCIA cover, around the back, and into the OPL2LPT +5V header. But when ~~nut~~ in use, this cable hides neatly ~~begine~~ the PCMCIA door.		At this point the BadgeBay™ hardware was more or less working. A few weeks later I ordered my soundcards. The CVX4 does not need any external power, but the OPL2LPT does. It has a mini-usb connector to power it from a nearby USB port, which this laptop lacks. Powering it from any external source works fine but is clunky. The OPL2LPT kit already has pads for a DIY power header. Since the ground was already connected trough the pins in the port and/or shielding, I again only needed to worry about the +5V. So I added another red wire to my already existing splice near the fan connector and made this one long enough to reach all the way from there to the left side of the laptop, trough the PCMCIA cover, around the back, and into the OPL2LPT +5V header. But when not in use, this cable hides neatly behind the PCMCIA door.

	<gallery>		<gallery>

Peetz0r at 23:06, 16 April 2018

2018-04-16T23:06:02Z

← Older revision		Revision as of 23:06, 16 April 2018
Line 140:		Line 140:
	==SoftPaq==		==SoftPaq==
	[[File:Compaq_LTE_4-50E_wallpaper.png\|240px\|thumb\|right\|The original wallpaper, from SP1585]]		[[File:Compaq_LTE_4-50E_wallpaper.png\|240px\|thumb\|right\|The original wallpaper, from SP1585]]
	[[File:Compaq_LTE_4-~~50E_rompaq~~.~~JPG~~\|240px\|thumb\|right\|SP2341. They called it ROMPAQ.exe]]		[[File:Compaq_LTE_4-50E_rompaq_2.png\|240px\|thumb\|right\|SP2341. They called it ROMPAQ.exe]]
	Somewhere on a dusty corner of ftp.hp.com all the original drivers and firmware and other stuff is still there in the form of SoftPaq's. Those are numered items, consisting of usually a .txt and a .exe file, where the .exe is a program that self-extracts and wrtes to a diskette. The only way to make this work is to run this in qemu, write to virtual diskettes, and copy all the stuff to directories on the CF card which had MS DOS and Windows. Some of the stuff are just installers for drivers, but some are supposed to be bootable. These things are just DOS programs packaged with a specific DOS variant, but they also run on normal MS DOS. In one case I had to disable EMM386 to upgrade the bios, but it worked just fine.		Somewhere on a dusty corner of ftp.hp.com all the original drivers and firmware and other stuff is still there in the form of SoftPaq's. Those are numered items, consisting of usually a .txt and a .exe file, where the .exe is a program that self-extracts and wrtes to a diskette. The only way to make this work is to run this in qemu, write to virtual diskettes, and copy all the stuff to directories on the CF card which had MS DOS and Windows. Some of the stuff are just installers for drivers, but some are supposed to be bootable. These things are just DOS programs packaged with a specific DOS variant, but they also run on normal MS DOS. In one case I had to disable EMM386 to upgrade the bios, but it worked just fine.