It might seem crazy to ask whether Tesla’s a car company – they certainly make cars, and on paper, cars are about 82% of their YTD revenue as of the third quarter of FY2017. However, I’m going to argue that they might not be a car company, but rather an energy company that makes cars, and there’s a few things that make me believe that. Continue reading
I recently bought an HP OmniBook 430 that needed a system ROM card, which has to be on a linear flash card.
Creating such a card, however, was a bit of an ordeal, so I’ll quickly document what exactly I did.
Ultimately, I used a ThinkPad 365XD, but the card I used would’ve been usable on most any laptop with PCMCIA. (I tried a Fujitsu Lifebook P1620, as well, but had trouble with finding sufficiently old Linux that worked with its hardware… although now I think I could have used something more modern, now that I know what I was doing wrong.) I used a Viking Technology 24 MiB card, that was an Intel Value Series 200 card. This is a 3.3/5 volt read, 3.3/5 volt program card, using Intel StrataFlash, or what we’d now refer to as MLC flash. Complicating matters, this card did not have attribute memory, and was completely blank, meaning that many tools couldn’t automatically figure out what it was. (I’m still not sure if it’ll actually work in the target device, partially because of being Value Series 200 – if not, I’ve ordered a Series 2+ card, which is likely a better choice anyway – but my goal here was to successfully program it, and that’s definitely been done.) And, for software, I used Damn Small Linux 4.4.10, plus the DSL MTD kernel modules from here.
In a root terminal, I issued the following commands, after saving mtd-modules.tgz in /home/dsl/.
tar -xzf mtd-modules.tgz
modprobe pcmciamtd buswidth=2 force_size=24 vpp=50 setvpp=1
cp /KNOPPIX/etc/pcmcia/config /etc/pcmcia/config
(OK, in reality, I issued a bunch of other commands, but those are the ones that were actually important, I think.)
At this point, I added two lines near the beginning of the file:
class "memory" module "pcmciamtd"
Then, I changed the binding of Anonymous Memory from memory_cs to pcmciamtd, later in the file.
After saving that, killing cardmgr, and relaunching it, I found that /proc/mtd listed the device, and dmesg showed that it was configured (and that CFI had successfully figured out what kind of flash chip it was working with)… but there was no device node. Apparently MTD didn’t actually make nodes automatically, back then, so a quick
mknod /dev/mtd0 c 90 0 took care of it. At that point, I could simply cat the firmware image to /dev/mtd0, and it flashed it successfully, which could be verified by ejecting the card, reinserting it, recreating the device node, and running cat on that device node.
Hopefully, if someone needs this, it’s available as a reference now.
If you’re using a Windows 10 laptop at anything other than the default scaling factor for your display, you may encounter an issue where closing the lid causes your window positions and sizes to be forgotten. I discovered this on my MacBook Pro Retina, which I run at 100% scaling (the default is 200%). This may also apply on Windows 8.1, but I haven’t tried it on this hardware.
In Windows 8.1, Microsoft introduced a new model of handling DPI scaling, that allowed different monitors to have different scaling factors. This is useful for situations where you’re running multiple displays of vastly different density, as it’ll make applications appear roughly the same size on all monitors.
However, at least in Windows 10, there’s a problem with this. Windows detects displays when they’re attached, and determines a proper default DPI and applies it. Once that is done, it applies your preferred scaling factor to the display. The problem with this is that closing the lid on a laptop effectively detaches the display, and opening it back up causes redetection. There’ll be no problem if you’re happy with the default scaling factor, but if you’re running a non-default scaling factor, this can cause huge problems. Apps can get stuck in the old scaling factor, windows will be rearranged, and windows will be resized. A workaround for this problem (if you don’t need different DPI for each monitor) is to disable Windows 8.1 DPI scaling, which on 8.1 could have been done by checking the “Let me choose one scaling level for all my displays” checkbox. That checkbox, however, is no longer available in Windows 10, but the registry key that it changed is still available, at
HKCU\Control Panel\Desktop\Win8DpiScaling. Change it from 0 to 1, reboot, and now all displays should have the same DPI, and closing your lid won’t change your window layout.
Obviously, there’s an underlying bug in display detection that Microsoft needs to fix (as the feature that I’ve disabled actually is a useful one). However, for my case, where I’m happy with all displays running at the same scaling factor, the old way of multi-monitor scaling (as used in Windows 98 (the first version with official multi-monitor support) through 8.0) works perfectly fine.
It’s rather tricky to get Windows 10 onto a WinBook TW700, between WIMBoot’s inefficiency, the inability to delete things from the preload, and the limited storage available on a TW700, so I thought I’d write this quick guide on how to get the device updated. These instructions should work on any WIMBoot device – or, for that matter, any Windows 8.1 Update (and possibly earlier versions of Windows, I’m not sure if Win10 will run from 8.0 or 8.1 pre-Update) device that’s short on space. Please note that your profile and apps will NOT be migrated – I’d use User State Migration Tool, from Windows 10’s Assessment and Deployment Kit, to save profiles, and then restore them after you have the device reloaded. I’ve not used USMT in quite a few years, though.
Following this procedure will result in the loss of all data and applications on the device, and I will not be held responsible for data loss as a result. You are responsible for ensuring that you can get everything restored.
Here’s what you’ll need:
- Two USB thumb drives of 8 GiB or larger capacity (one of these may not be necessary)
- A MicroSD card or a third USB thumb drive of 8 GiB or larger capacity
- A USB hub, keyboard, and mouse (shouldn’t be necessary, but it’s useful in case something goes wrong)
Here’s the procedure that I followed in a nutshell:
- Create a USB recovery drive and put it in a safe place. This will allow you to go back to the factory preload at any time. This is a good practice even if you plan on staying on Windows 8.1.
- Reset your PC (Microsoft directions, go to “Remove everything and reinstall Windows”). This is necessary to get free space back.
- When the Out-of-Box Experience comes up, connect to a wireless network, but do not log in using a Microsoft account (you don’t want any OneDrive data downloaded), and disable Windows Update (you do not want updates taking up the storage space you just freed).
- Use the Media Creation Tool on another Windows machine to create a install USB drive for Windows 10 Home 32-bit English (US), then connect that USB drive to the tablet and run setup.exe on it. You may not need to do this, it may be possible to use the Media Creation Tool’s ability to update the computer it’s running on, but I played it safe.
- The Windows 10 installer will mention that you need more space to install. Either use a USB hub to connect another thumb drive, or insert a MicroSD card, and select that drive in the installer.
- I personally chose to change the settings that would have migrated my profile and apps, and chose to only install the OS. This one’s up to you, though.
- Proceed to wait a while, while Windows 10 is installed. There may be a few points where the device freezes during boot, just shut the device off by holding the power button down, then release the power button, wait 5 seconds, and press it again, it will proceed normally.
- Go through the Out-of-Box Experience and adjust settings to your liking. Once this is complete, the device may be sluggish for a while, as it’s performing a lot of background tasks (updates, driver installations, and the like). Let it complete these before continuing.
- Delete your previous version of Windows. Why keep it around, when it’s just the preload missing the software that came with it, and you’ve got a thumb drive with the USB recovery drive?
- Somewhere along the way, a driver update will have happened, and Windows will have decided to run at 125% zoom. If you like this, leave it alone. If you don’t, go to Settings, System, Display, and change the size of text, apps, and other items to 100%. Do note that Modern UI apps are rendered smaller than in Windows 8 (and currently don’t appear to respect the system scaling setting), and Universal apps tend to have smaller UI elements than Modern UI apps did in Windows 8. However, Win32 apps are rendered the same at 100% as in Windows 8. This one’s up to personal preference, really.
That’s all there is to it. (Well, there may need to be a Bluetooth driver update, I haven’t checked that fully yet…) There’s still some glitches in Win10 (the on-screen keyboard only really works the way it did before when in a Universal app – Modern UI apps at 100% don’t quite behave right, and Win32 apps don’t move out of the way at all), but generally, things should work. And, it’s faster, lower RAM usage, and lower disk usage than before (Win10 has a much better compression mechanism).
So, Micro Center is selling Windows 8.1 tablets for $60. No, really. That includes a Windows license, a quad core Atom (that’s right, this isn’t even RT), an IPS display, and a friggin’ Office 365 Personal license (even with rights to install on a desktop or laptop)! Now, it does only have 1 GiB RAM, and worse, only 16 GiB of eMMC, so there were corners cut. However, even with those limitations, the price really does seem a bit too good to be true.
Then again, it’s only $60, and Micro Center does take returns (and there are plenty of open box units for $48, although I strongly suggest avoiding those for a couple of reasons), so… I ultimately couldn’t resist (if nothing else, it’ll be a decent device for running the excellent VCDS Volkswagen diagnostic tool by Ross-Tech), and I’m typing this post on it. Continue reading
Putting some quick notes up regarding configuration of a MikroTik device to behave like a consumer router, where accessing the router from inside accesses the router, and accessing the WAN IP from either inside or outside accesses an internal host via port forwarding. Continue reading
So, I finished resurrecting my mainframe the other day.
When I was in Kansas City for KansasFest, I bought an RS/6000 7011-250, which uses the smallest chassis capable of holding 32-bit MCA cards that IBM ever produced – for comparison, I’d say it’s about the size of a Quadro 610 or Power Mac 6100, albeit a bit deeper. (It was also the first PowerPC machine ever produced (predating the PowerPC Macs by a few months), using a 66 or (in my machine) 80 MHz CPU.) This allowed me to physically downsize the machine significantly with minimal loss in functionality.
I installed the P/390 card set and installed AIX while at KansasFest, but was unable to get the mainframe actually running for several reasons. Ended up putting the project on hold for various reasons (including building the Mimeo).
Lately, decided to get back at it. Continue reading
I’ve wanted to try Matias’s new keyswitches since I’ve heard of their release, and finally, decided to go ahead and get a Tactile Pro 4, as my local Micro Center had them in stock.
Matias has developed their own clone, the Matias Click switch, of the Alps SKCM tactile keyboard switch (specifically, the simplified white version), and installed it in their long-running (Mac-optimized) Tactile Pro series, creating the Tactile Pro 4. The previous model, the Tactile Pro 3, used Fuhua switches, and in my opinion, these switches had downright terrible quality. They’ve also cloned the SKCM cream switch, which had rubber damping, as the Matias Quiet Click switch, and are using it in the new Quiet Pro keyboard, although I’m not reviewing that switch.
So, I don’t typically review keyboards on this blog, and I’m not sure why I haven’t. So, here goes. Continue reading
Decided to build the AC side of the power supply today. Powered on, voltages looked good, no magic smoke, nothing getting hot.
That went well, so I decided to stuff the video section and power it on again. (Pardon the filthy monitor, I had to grab an old clunker from my storage unit, I didn’t want to risk the Dell 2001FP, nor did I expect it to take that signal well.)
Clearing the video had an interesting problem, though – once I removed the clear jumper and the video returned, the underscores went away, but the blinking @ signs didn’t!
Anyway, I decided to continue onto the processor section – the video section behaving like that was actually promising, because it was almost all working.
Resetting the processor showed that it was definitely working, and the video section was even responding to the processor section – a line of @ signs would get replaced by slashes, for instance.
With a study of the schematic, I decided to figure out what would cause this problem… and decided to swap the 2504 that holds cursor position with one of the ones that holds character bits. Sure enough, the problem moved:
So, I now have a working(ish) Apple-1 clone. Tomorrow’s project will be to put the finishing touches on the board – solder the slot connector on, solder jumpers for the cassette interface and BASIC RAM, install the ACI, and celebrate (even though that shift register needs replaced).
The project won’t be done, though (and the computer won’t really be usable until some of this is done, and it definitely won’t be safe due to the AC section being exposed) – I need to get a keyboard encoder (waiting on a solution for that one), get a slot expander, wait for the CFFA1 to arrive, and work on my case (which will be a stained oak base, with 4″ aluminum standoffs supporting a plexiglas top above the board and power supply, and a plexi case around the AC section of the power supply). Also, I’ll do a similar, much smaller case for the ][ Plus keyboard.
I know, it’s an out of focus cell phone shot, but I’ve already got it drying after cleaning the flux, and don’t want to take another shot.
Resolution on the capacitor issue was simply going ahead and using the supplied caps, as they should not negatively (and may positively) affect function, and will only negatively affect authenticity, of which this has none anyway, so…
Yes, I got the top 2400 µF cap so that you can’t read the printing on it. Purely a cosmetic issue, kicking myself for doing it, and I caught it too late to easily fix it. (I could obviously fix it now, but it’d generally be a pain, and some of that is on the ground plane section of the power supply, which is a bear. Not as bad as the 7905’s ground section, but bad.)
Plan for tomorrow: build the AC side of the power supply (that is, wire up the transformers), and go for first power up to test the power supply section.