Friday, 19 February 2021

Is that racist?....

 I'm no extended universe aware person when it comes to Star Wars, but something has been baffling me lately... Admiral Ackbar... Who?


Yes him... The guy in the big ship (see how noob I am talking about this stuff?) in Return of the Jedi who says "Its a trap" well, he has always looked rather aquatic to me, like a shrimp or something a fish.

I assumed this was just his thing, the designer had a thing for fish... 


Instead I found out he's actually from the species "Mon Calamari"... yeah... Calamari... You know.... Cooked Squid.

And I look at Ackbar there... and I think about a squid.. and I think... "Oh... Is that racist?"



Thursday, 18 February 2021

Ship Diorama Build Blog : HMS Rodney : Pt2

This base build is very time consuming, mainly due to the requirement to allow layers to dry and set before proceeding onto the next layer.  As such when I move onto the two other models I'm going to make both ships at the same time, this is so that I'm using the same materials at multiple times across the pair.

As mentioned before the first colour layer was put down and covered, I have since repeated this, layering the tissue paper and 50:50 PVA to water mix and softening or adding wavelets as I've gone.



As this dried you can see the previous colour layer coming through quite strongly.  But before more colour could go on it needed now to dry completely.

So, I set about mounting the black plastic hull base from the model itself.

First a test fitting into the wave front for the bow...


 Then I spent time cleaning up the base to allow the line of the hull to sit into the sweeping water feel now built up...And once I was happy I drilled two holes in this base...


Through them I then pushed a cocktail stick...





Cutting it neatly and then adding a dot of superglue to fix them in place, these are now through the plastic and into the polystyrene, but they're not permanent, the base can be pulled off, it's only held by a little excess PVA and the sticks.


Adding the weight, stuck down with a liberal swish of superglue completes this preparation...


And a hull test fit confirms things are going to work out....


Next, with thinner I took aquamarine and blue/green acrylic paints and gave a nice but randomly shaded 


At this point the base has been left to dry for 24 hours.


I plan to pick out the wave crests with some white and add a little more detail to the wake, but the base colour, wave shape and layers of modelling are done.

We'll return to the base only for the edges needing colour and building our frame and badge.

On to some actual model painting!




See the other parts here:

Sunday, 14 February 2021

Ship Diorama Build Blog : HMS Rodney : Pt1

The eagle eyed of you will have seen the slew of short model videos going onto my YouTube Channel, and the great and good among you will have subscribed there already, if not the YouTube link is always right there in my blog.

But my new project is a blog exclusive, I'm not planning on filming much of this build, instead we're going to use more high-resolution photographs taken on my phone.

It's also going to be one of the biggest "things" I've ever built.  I've returned to modelling as a hobby in my middle age, but as a kid I was very keen model maker and I had literally hundreds of planes in zoom poses hung from my bedroom ceiling.

But I also had a small fleet, I had the HMS Belfast, HMS Hood and HMS Illustrious in 1/600 by Airfix on my window sill.

In fact in my mid 20's I actually bought and build a second HMS Belfast, which I actually left in my then rented house when I moved out, as I could not find anywhere to put it, but couldn't bring myself to throw her away.

Anyway, I've now decided to start a new fleet and I've decided to go with a 1/700 build of one of my favourite ships HMS Rodney.  Historically this lends some symmetry to my old HMS Hood, as the Rodney exacted terrible revenge by helping to sink the Bismark.

This smaller scale is perhaps my challenge, and the level of detail I want to bring to the model is going to likewise be a challenge.  And I am on the hunt for more detail sets and photo etch to put into use before I get started.  As such, I need to start the model somewhere other then itself, and I've decided on making a diorama.

I can't possibly use epoxy, it's too cold to go work outside and working in my office, I have to be able to put my model making kit all away, so a long cure time is out of the question.  I'm therefore going to start small and simple... I can after all lift the ship back off this base at anytime.


The first step was to use the included base as a template, I tried on card, but immediately saw the materials I had at hand would cause it to disintegrate.  So I found this piece of 2 inch thick polystyrene from a package, and started to mark out the outline.


Next I cut the large sheet to roughly the right size and broke off the excess material.

Next I needed to do some preparation work, I decanted some of my PVA into a spare jar, which has a lid, putting in about 60g of the glue and 80ml of water I shook them vigorously until I had a quite runny PVA mix.






I also retrieved a single piece of aluminium foil roughly the size of the whole base, and I started to roughly layout and gently manipulating the foil to fit like the first layer of my wave effect.
Once I was happy I slipped these aside and painted a layer of neat PVA quite thickly onto the base and then started to place the foil back in place.
making sure to let the foil fall as it liked.

Once it was completely covered I then took single sheets of toilet paper and the PVA water mix and started to layer them over the foil, with the aim of softening the harsh lines, but keeping the pattern random and natural.


Once complete I did a test fit of the plastic base.

And from that alignment started to layout very thin lines of paper and foil atop the current layers, to make an inflection of a bow wave.


A quick test fit.


And once I was happy I got the acrylic paints out, very dilute with water I started with a deep aquamarine gloss from Revell.  Adding a hint of green gave this strong bold colour a real flare of effect.

But, this is only a hint layer and so another layer of toilet paper, single ply this time, was used with the watered down PVA to activate the paint and bring it through.


This further softened the overall wave effect, this is notcable most in the left of field and in the bow wave being much softer and appearing to roll.


A final smattering of watered PVA and I set this whole thing aside.

My plan going forward is to let it dry completely, then trim the excess foil and paper from around the edges, before hitting the glossy acrylic again, but that will be softed with white/grey.  And I'll gloss varnish after that, before picking out the waves with white and giving everything a second gloss varnish.

I've seen a recommendation to use a high gloss varnish of another type, so we'll see... either way, for my first base ever, I'm happy so far, and... it's kept me out of trouble for two and a half hours making it.



See the other parts here:

Friday, 12 February 2021

Debugging Techniques

 As a programmer there are many approaches to a take in solving a problem, I remember in my A-Level they talked about trace tables... A lot... I've used them now and then, but almost immediately machines were running so quickly as to make humanly computing any meaningful number of permutations near impossible... and we're talking only a 25Mhz machine.

Far more useful therefore was a decent watch value in a debugger, improved immeasurably by conditional break statements.

Even so there are always times when you need that holistic overview, my favourite approach for this is a huge wide whiteboard.  Many an hour have I spent around a whiteboard laying out the schemes of madmen and managers; the greatest compliment is then when finding that said folks have taken a cheeky photo and your whiteboard machinations appear in the manual.

But one of the best problem solving solutions is to share it, a problem shared can often become a problem halved; unfortunately not always for a programmer.  You see people are a creature of opinion and social status, this means you can often run into folks who believes their opinion is more valid than yours, which maybe so, but if their opinion means starting the whole problem over again it can often be more detrimental than asking for their help.  For help becoming opinion leads only to their being demons in the cupboard.

So what then?  Talk to one self?

And you know I think really rather that is one of the key approaches, talk to yourself.  Quite useful in the current pandemic too.

We have a term for this in Computer Circles, and we detract from the self by making our conversation focus on another object, such as a rubber duck... https://en.wikipedia.org/wiki/Rubber_duck_debugging

Or of course you can find your own devices....



Wednesday, 10 February 2021

My Desktop PC History

My PC history and I literally mean PC's, so we're talking after my Atari ST, this is a list of the machines I've owned and used in order and a little bit about what I did with them.

486-SX-25 (1994)

The first PC I used was built by a company based in Baseford in Nottingham, it was at college and was equipped with an Intel 80486SX, it ran at 25Mhz, ran DOS 6.2 and a netware network layer.  It had 4MB of ram and basically was very much locked down, that was until we figured out how to quit out of the netware login screen (repeatedly CTRL+C whilst hitting enter fast).  The college had loads of these machines of this specification, the three main IT labs of course but then there were two more directly outside one of the lab doors, another in the head of Chemistry's office and a bunch in the library.

I primarily programmed in Turbo Pascal on these machines, I remember playing about with writing my first games on this in EGA graphics mode.

486-SX2-50 (1994)

My first home PC, it was from Watford Electronics and had their own ISA riser connecting to a dual speed CD-ROM, I remember Encarta amazed me, as well as working out how to just play CD's whilst programming.  I of course did my college work on the machine, and I remember my brother did his too.

The machine came with 4MB of RAM and a 200MB hard drive... MEGABYTE... I remember windows 3.1 ate into the disk significantly.

But DOOM came into view, now at the time I had no idea really what SX meant, but it had effects on DOOM's speed.  One of them was the maths.

I actually programmed around the limitations of t he SX chip without realising it and this came back to save me (or curse me) later.

Later we got Dark Forces and another 4MB of RAM, giving us a total of 8MB in this machine as I went to Uni.

But basically the SX had no floating point unit, it had only integer mathematics as well as a bunch of other operations being missing.  It was basically a DX chip which had failed QA and had come part of it disabled, but this was a "2" which meant it ran twice as fast as the machines at college.  And that speed difference was reflected in my little home brew games suddenly running twice as fast.

This remained my main and only PC going to Uni, but in my second year of Uni, sharing this machine with my A-Level studying brother I needed my own and these "Pentium" machines had been released.

Pentium-100 (1996)

The power of the penium, with the EDO ram SIMM's was so massive compared to the 486, and this was the first machine I started to program in C on.  Indeed, it was also the first machine I wrote Java on and even played with Linux.  But I never loved this machine.

Running at 100Mhz, it was blisteringly fast to me, but I was still using DOS 6.22 and Windows 3.1 for the most part.

I should have, it was the first machine I bought with my own hard earned money, I did keep it until my final year at uni, but by then I had started to build my own machines.... But I'd also been to work in IT.

HP Pentium-166 (1998)

This was a machine at work, it was mainly a windows 95 platform for me to work with, I soon had Windows 95 at home too, so things balanced up.  All I used this for was some very basic database work, which the prior incumbent in my job had left (and which was awful).

Compaq Pentium-II 233 (1998)

Another work machine and at 200Mhz, it seemed like the things of legend, but this was a compaq deskpro to which all the analysts and myself upgraded, with  massive 17" CRT monitors, they were really nice machines.

I did a bunch of Pascal programming on it, a bunch of Cobol and some database work (I think it was in FoxPro).

Pentium-III 300 (1999)

Returning to Uni for my final year I built this machine myself, I remember this was a slot-1 processor, and I put a whopping 32MB of RAM into it.  I wrote my dissertation on it and networked it to my older Pentium 100.

Voodoo3-2000 AGP.... Which I only sold in 2013 on ebay, at a profit.

Cyrix-150 (1999)

This was actually my pentium 100, but I found the Cyrix chip for sale for only £10 at maplins so bought it and stuck it in the old PC, to find it was a massive performance improvement when compiling and running both C and Java.

Celeron-III 450 (1999)

This was a machine I actually built for a customer, I spent a bit of time making PC's and making money doing so in the late 90's.  And this was one which stuck out to me because it was such a nice performing machine, it included a graphics card (I think it was a Voodoo3-3000).

The build was with a gigabyte motherboard using slot-1, but the processor was socket 370, buying it and using a daughter board was cheaper than buying a socket 370 motherboard, and performed no differently.  It actually made adding the cooler so much easier.

Pentium III 500 (2000)

I bought this after uni, just a new chip, with 128MB of RAM as I set off away from uni.  I just played a lot of games on this machine, dabbled with Java, but I didn't have the compiler suite we used at work to my programming was mostly all in the office.

Pentium III 500 (2001)

This was the office machine I had at the time, I'd had one before, but don't recall it, this one however was by the local computer firm in Redditch and I remember it was a 500mhz Pentium III.

GeForce... At some point at home in 2001/2 I got the first GeForce card at home and started to babble with OpenGL on Linux.

Pentium III 1ghz (2003)

Another office machine, this was a bod standard HP I think, the job here was C++ programming, but coming from a pure Borland using history (all the way from college to now) I was suddenly not in a Borland using shop and... well... I didn't stay at this job very long.

Pentium IV - 1.5ghz (2004)

A prescott Pentium 4... at the high speed of 1.5ghz, this was my first hyper threaded machine, it was built from the ground up for gaming... so it had 1.5GB of RAM (the most I could afford)... the dual thread pentium 4, overclocked to 2ghz on air.

A pair of GeForce 8800GTX in SLi.

I bought it to run Battlefield 1942 really well, and was really very good.  I also played national league Day of Defeat and started my dual obsessions with World of Warcraft and Eve-Online on this machine.

Core 2 Duo 3ghz - Wolfdale - 2.3ghz

I built this machine for my father, he didn't appreciate it at the time.

Core 2 Quad Q6600 - 3ghz (2007)

This was my main driver for years, and the machine I first put into the Cosmos 1000 case.  It had various RAM, disk, graphics configurations until the last iteration being a GeForce 260 GTX (squared) so this was two GeForce 260's on the same card in SLi together.... It was really good.

I spent time coding for Lordz Game Studio on this machine, as well as playing lots and lots of games.

Core i7-920 (2012)

Yeah, we're at Core i7.... the best I could accord for the i7 release set and it went into the same case as the Q6600 was in.  This machine was a main-stay until I actually swapped out the Core I7 (4 cores 8 threads) for a Xeon which was 6 cores and 12 threads... I did that in like 2016... so I've had 12 threads at home for a long old time.

Ryzen 5 3600X (2018) -> Ryzen 9 3900X

Team Red.... Aside from the cyrix I've always, always been Intel... Ryzen turned my head, and the 6c12t 2600 was the first I could get my hands on.  But the motherboard was purchased with upgrades in mind and the same machine now has a Ryzen 9 3900X 12c24t.

It was a mchine built around the 64GB of RAM, dual m2 NVMe and a stack of 4TB disks, all in a corsair obsidian case.

Saturday, 6 February 2021

Sorry... What was that measure?

 I've a bit of an eye for oddities in product listings... and this one caught me...

This is for a door latching system and its the weight thng at the top, first of all they can't just say "takes between 1.2 and 1.6 kilos of force to open", instead they go with this very odd metric of 1.5 bottles of 4L water.

So... one and a half bottles of 4 litres of water....

Very distinctly not six litres of water... And the strange thing is I'm pretty sure a litre of water weighs a kilo itself, so one and a half bottles of 4 litres... That'd be 4 + 2 giving us 6 in total, six kilos, which isn't mentioned.

It is just all round odd... That's all I've got for you, move along... move along I say!

Thursday, 4 February 2021

The most insidious file on Windows....

The most insidious file on Windows....

Microsoft.DataWarehouse.Interfaces.resources.dll?

This particular file lives in my 

D:\Program Files\WindowsApps\Microsoft.Office.Desktop.Excel_16050.11029.20108.0_x86__8wekyb3d8bbwe\Office16\ADDINS\PowerPivot Excel Add-in\sk

folder.... The key feature of that hideous path is that it's in my D drive... this is my second drive and you'd be right to ask why it has a windows installation on it?


Well, that's the drive that came with my laptop, and so it had the spyware, adware riddled carcas of a windows installation I never used, I just installed my own new NVMe drive and went with that.

This installation of windows has been taking up like 15GB or more of Space for over two years to it was time to nuke it.  The problem?  You can't just remove windows trusted installer files.

My way around this is to go into the properties, into advanced, set the owner user and god for that file to be me and remove the other windows junk user groups and such, and make sure everything is inherited down the line.... 

And I did this, removed windows, program files and windows and program data.... all except for this one file.

Which is totally insidious.

It won't disappear despite my being that very user/owner and even having used "runas" to launch explorer and cmd as myself for 100% certain.

The security settings can't be set....



It is literally moments like this where I hate that I can't fully control my operating system.

Sure, this is an edge case, who would really want to let windows delete something critical, but I've clearly worked around the issue, jumped through enough obscure hoops and set myself in the driving seat that the OS must know I'm up to something I know I'm doing... and I'm doing it with their UI, so not with some obscure script, so I'm clearly NOT a baddie.... sort of.

Yet, I can't delete a file, the file is actually zero length... it's just crud and evil.