Password strength
Yes I see you trying to login as me. Â Yes I blocked your Russian and Ukrainian addresses.
What are you so desperate to see here?
There is no deep secret files, or drafts.
If anything I get into trouble for revealing too much when I do find stuff.
Take it easy man, there really isn’t anything to see here.
(this is a guest post from Tenox)
WYSE Unix Virtualization Challenge has been officially won by Mihai Gaitos of hawk.ro. He received $100 prize via PayPal. Congratulations!
WYSE Unix has now been virtualized and can run in Qemu via Curses mode, or modified Bochs due to character map issues and vanilla VirtualBox!
Mihai has posted some gory details of the installation challenges on his website.
Ready to run image with modified Bochs binary for Linux is available here.
VirtualBox OVA file available here.
For hard core fanatics, the system comes with SLIP/slattach so you should be able to network it much like Dell Unix.
Special thanks to:
Andrew Gong for finding a tape image on eBay
Al Kossow of bitsavers.org for recovering the tape image
Michal Necasek for patching up the original floppy disk image
(this is a guest post by Tenox)
Finally someone made a distribution with CDE as default eyecandy. I’m happy.
Enter CDEbian!
Speaking of retro!
totally!
It’s the best thing since GTA Vice City!
It’s kind of amazing there is that much uploaded to youtube these days. Â I guess with enough archivists out there, you never have to leave those oh so innocent and simple decades. Â Or at least the ‘music channels’ are the perfect thing to listen to, while reading olduse.net.
(this is a guest post from Tenox)
The second virtualization contest is now on! Similar to the previous one, the winner receives $100 via Paypal and the submission is posted on this blog! Hopefully this one will be little bit more challenging. 🙂
The subject is the rarest of the rare WYSE Unix!
The progress so far: A few years ago I came in to possession of a set of floppy disks pictured here:
Thanks to Al Kossow from bitsavers.org the floppy disk content has been recovered. Michal Necasek of OS/2 museum successfully converted them in to an usable format and made some modifications to get them to boot on VirtualBox:
Couple of years later, thanks to Andrew Gong, a WYSE Unix tape has been found on eBay:
More recently Al Kossow was able to read the tape in to an image, which now I have uploaded to my web server: wyseunix321a.zip
The next step is yours! Install the whole system on to a hypervisor of your choice, document the process and supply a vanilla boot image or VM.
The winner shall be the person who will first post a comment declaring success including a screenshot and can further prove it by emailing emailing me the submission shortly after. If the comment gets blocked by spam filter, don’t worry the original submission time will of course count. Oh and almost forgot: I also need aclock binary for it, however if there is no compiler and the standard SysV binary works fine, you are exempt from the requirement.
The catch? Looks like floppy disk trouble. The boot disk is fine after it has been fixed up by Michal. The Base floppy looks like has same content as boot. Copy Tools is very small. Looks like it may be truncated. Hopefully not, but if yes I count on your creativity. Remember that Dell Unix is an exactly save release of SystemV/386 and did not have or needed copy tools to install.
Good Luck!
Update: Looks like the contest has been won by Mihai! Congratulations!
(this is a guest post by Tenox)
This is a step by step guide on how to install Venix/86 on PCem, by runner up of Venix/86 Virtualization Challenge – Mihai Gaitos of hawk.ro. Thanks for a great work!
Rebuilding Venix for PCEM:
First, in order to avoid problems with weird HDD parameters I chose a reasonable hdd geometry – 512 cylinders, 8 heads, 17 sectors (most drives back then had 17 sectors).
HDD geometry:
BIOS Autodetect:
(answer “Y” here)
The obvious approach of Booting the XFER.IMG and then switching to BACKUPn.IMG doesn’t work, failing with “Soft error”:
Continue reading
Blocked!
Ugh I’m sure I’m not the only one that has this issue. Â So before google drive, and friends were a thing, gmail gave us 1GB of mail space (at the time why it was called ‘G’ mail). Â And what better way to make files available between machines than to email them to yourself?
Well this worked for YEARS then they started to block some extensions, and now they block damned near everything. Â From their ‘Learn more’
As a security measure to prevent potential viruses, Gmail doesn’t allow you to send or receive executable files (such as files ending in .exe). Executable files can contain harmful code that might cause malicious software to download to your computer. In addition, Gmail doesn’t allow you to send or receive corrupted files, files that don’t work properly.
You can’t send or receive the following file types:
.ade, .adp, .bat, .chm, .cmd, .com, .cpl, .exe, .hta, .ins, .isp, .jar, .jse, .lib, .lnk, .mde, .msc, .msp, .mst, .pif, .scr, .sct, .shb, .sys, .vb, .vbe, .vbs, .vxd, .wsc, .wsf, .wsh
Messages containing the types of files listed above will be bounced back and returned to the sender automatically. Gmail won’t accept these file types even if they’re sent in a zipped format. Here are some examples of zipped formats:
.zip, .tar, .tgz, .taz, .z, .gz, .rar
Well isn’t that great. Â Of course when I’m uploading source I tend to include executables, custom batch scripts to either clean or prepare, and sometimes run whatever it is I’m doing. Perhaps libraries, jar’s and maybe even device drivers.
Thinking the email attachment had been lost I was looking to see if I can forward it, when I stumbled onto this interesting bit:
The show original option!
This lets you view the email in it’s un- formatted state, which also includes the attachments!
So from here it’s a simple matter of saving the file to your hard disk. Â It is important that you ONLY save the base64 portion not that headers. Â I guess this is a pain for multiple attachments as b64 doesn’t read MIME containers.
If you look at an email it’ll roughly look like this:
MIME-Version: 1.0 Received: by 10.64.9.141 with HTTP; Tue, 29 Oct 2012 13:33:16 -0700 (PDT) Date: Tue, 29 Oct 2012 13:33:26 +0800 Delivered-To: [email protected] Message-ID: <CA+rfG9Z-5Ej7iuXs36a_Lryqw+gs52GMUEFE9XPrSswjHRxXqw@mail.gmail.com> Subject: doom? From: Neozeed <[email protected]> To: The Number One Guy <[email protected]> Content-Type: multipart/mixed; boundary=001a11c3b874d1eaf704e9dde937 --001a11c3b874d1eaf704e9dde937 Content-Type: multipart/alternative; boundary=001a11c3b874d1eaf204e9dde935 --001a11c3b874d1eaf204e9dde935 Content-Type: text/plain; charset=ISO-8859-1 Don't lose this file! --001a11c3b874d1eaf204e9dde935 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Don't lose this file! =A0<div><br></div> --001a11c3b874d1eaf204e9dde935-- --001a11c3b874d1eaf704e9dde937 Content-Type: application/octet-stream; name="DOOM_SRC_102813.7Z" Content-Disposition: attachment; filename="DOOM_SRC_102813.7Z" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hncxub2b0 N3q8ryccAAPH+QLokKMEAAAAAAAkAAAAAAAAAKm3ezkABoLDcK0hSHl0xaeKFIsLY1Idc7MMQAtM jDXWS9Sc5PvtvOmy27+byH8YZTOBY65JnEi5L9U41YDw53Wi1/xxpcR8Az8yIfc7DjQIT0ULtATL
We start the file at the ”
N3q8ryccAAPH+QLokKMEAAAAAAAkAAAAAAAAAKm3ezkABoLDcK0hSHl0xaeKFIsLY1Idc7MMQAtM
line. Â I’m going to save it in notepad as “attachment.b64”
Now for the decoding!
I’m using b64, from sourceforge. Â However you need an ‘older’ version 1.4 as the newer version has a decode bug. Â Also
b64 -l76 -d attachment.b64Â output.7z
And this will (blindly) decode the attachment.b64 into output.7z. Â And from here you can extract the file without any issues.
As a bonus, if you have Outlook, you can just save the entire file as an .eml and open it in Outlook!
So easy!
Also for Outlook 2003/2007 users you may have to use this registry alteration to have them support directly loading of .eml files.
(this is a guest post by Tenox)
I used to use Veritas products (Volume Manager, File System and Cluster) professionally for quite a long time on Solaris and HP-UX. Except for Cluster, the software was exceptional for it’s time. Unfortunately after acquisition by Symantec and advancements of other storage technologies such as ZFS, the product suite disappeared from the radar completely.
Back to present time, I have a small x64 server that I use primarily as a NAS box plus run some applications, services and a few VMs. The machine runs Windows 2012 R2 Server which, for most parts I really like, with an exception of the storage stack, namely Storage Spaces. This is a completely botched feature both from functionality and management point of view. I don’t want to rant about it too much about it, so I just leave it as non working.
Unable work with Microsoft Bob of storage I have been looking for different alternatives, from using the Windows built-in VDS RAID-5 option, to moving entirely to a different OS. This is when I remembered that, some (OMFG!) 10 years ago Symantec has announced free Storage Foundation Basic, also available on Windows. Still continued and supported to this day, so obviously I wanted to give it a spin and evaluate whether it makes any sense to use such a dinosaur in a modern world.
I spun up a Windows 2012 R2 guest vm, added some data disks, downloaded the latest version 6.1 (released in 2014) from here and ran the installer.
Uh, that’s not me!
Ever have one of those days, where you suddenly get a weird email? Â Recently I thought the whole ‘google security’ thing was a bit over the top, then I get this fine email. Â I’m pretty sure it’s from a hotel I stayed at, looks like they had something there to MitM me. Great. Â But thankfully they used an old ass machine from the looks of it, so it triggered google.
You may want to check your security settings here, if you are using Google, with their security settings centre.
https://security.google.com/settings/security/secureaccoun
If you know your phone will work where you travel, and don’t mind the typical phone company overcharge for daring to leave the area, I’d enable 2 factor authentication as well.
(this is a guest post by Tenox)
I’m extremely busy with some matters and unable to spend much time with computer archaeology. I would like for some much overdue projects to progress independently of myself, so hopefully the community can participate and help out.
Let’s start with Venix/86 which has been awaiting my attention for a while. I have been recently contacted by Alex aka uav1606 who wanted to get it to work. I have since decided to open this up to anyone else interested.
To my knowledge actual install media did not surface so far. However a while ago I came in to possession of a boot disk and a backup of a live system, in form of nine floppy disks which look like a tar archive. In theory it should be possible to boot the xfer disk, format a hard disk and restore the backup system to get a working system.
VenturCom Venix/x86 running on a real AT/286
I’m offering $100 prize via PayPal to the first person who will run Venix/86 on an emulator of any kind (PCE, PicoXT, QEMU, Bochs, Vbox, MESS/MAME, etc NOTE: it doesn’t have to be strictly XT emulator as long as the system works), compiles Aclock and sends me a binary + complete working virtual machine. I will also of course publish it on this blog featuring all your hard work! It will be awesome to see your progress and collaboration in the comments 😉
Everything I have is here: http://www.tenox.net/get/venix21.zip
Update #1: From Frode van der Meeren who is the owner of the floppy disks: “The disk images are not corrupted, the disks only use a different track arrangement. The disks image format arranges the tracks by cylinders, storing head 0 and then head 1, while the actual disks arrange tracks by all cylinders on head 0 then all cylinders on head 1. If you want to mount the images into something else than Venix/86 then you need to rearrange the tracks in the image file.”
Update #2: the competition has been won by Jim Carpenter! Congratulations! Jim has just received the $100 prize. I have received detailed install instructions and will post it in a follow up post 🙂
Update #3: The winning entry, how to install Venix/86 on MESS/MAME
Venix/x86 running on MESS/MAME by Jim Carpenter
It was a real pleasure to see great community response, participation and most importantly to see Venix/x86 run again!
Stay tuned for another one 😉
