January 2026
M	T	W	T	F	S	S
	1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29	30	31

Archive for the ‘Power User’ Category

Looks like I might participate in the TRIASSIC-study to help compare TAMIS versus ESD for resection of non-pedunculated rectal lesions

Posted by jpluimers on 2022/05/06

As a follow up of Some links on removing colon tissue with Endoscopic Full Thickness Resection (EFTR), it looks like I might participate in the TRIASSIC-study to help compare TAMIS versus ESD for resection of non-pedunculated rectal lesions.

The reason I document is my earlier Tweet: [Wayback/Archive] Jeroen Wiert Pluimers on Twitter: “Meh result of the colonoscopy: – 2 polyps of ~1cm size removed – 1 polyp of ~2.5cm could not be removed now: it is in an odd place (grows over the LAR-resection seam) and needs team-discussion on what to do in a future procedure (hopefully colonoscopy, maybe larpscopy) 1/”

So I archived most links from searching for EDS and TAMIS (further below) plus the whole content of the [Wayback/Archive] TRIASSIC-study:

A multicentre, randomised controlled trial comparing TRansanal minimal InvAsive Surgery (TAMIS) and endoscopic Submucosal dIsseCtion (ESD) for resection of non-pedunculated rectal lesions.

Links (English and Dutch)

Read the rest of this entry »

Posted in About, Cancer, Health, LifeHacker, Personal, Power User, Rectum cancer | Leave a Comment »

Setting up a GitLab project so it is served over https as a gitlab.io and a custom subdomain

Posted by jpluimers on 2022/05/05

Last week, I posted about Setting up a GitHub project so it is served over https as a custom github.io subdomain.

Today it’s the equivalent, but on GitLab.

Why GitLab? Two major reasons: unlike GitHub:

it’s open source
provides way more granular control over permissions
allows a hierarchy of repositories on which you can specify that permission control

Already 2. and 3. combined are a huge advantage, though we will see that 3. also makes some of the subcases (hosting as user.gitlab.io from account gitlab.com/user where user is your username) is harder than the similar user.github.io, github.com/user combo.

So here we go, starting with a similar set of links:

The goal is to have

page projects as or under wiert.gitlab.io (like wiert.gitlab.io/wiert)
a gitlabstatus.wiert.me plain html (or maybe markdown) page project that eventually will show some status information (kind of like status.gitlab.com, but for different things).

The beauty of GitLab is that it supports hierarchies of repositories through groups and subgroups, so I already had these subgroups hoping they would cover both the first and second kind of page projects:

Steps I did

Since there are quite a few links above, here are the steps I took from my gitlab.com/wiert account and gitlab.com/wiert.me group.

Steps for wiert.gitlab.io/wiert

For wiert.gitlab.io/wiert, try A (failed in part, and therefore interesting to understand why):
1. Under leaf group gitlab.com/wiert.me/public/web/sites/gitlab.io, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert” (with slug “wiert“) so it would appear at gitlab.com/wiert.me/public/web/sites/gitlab.io/wiert
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Now I got in a confusing situation as the page indicated “There are currently no pipelines.”, but an enabled blue “Run pipeline” button:
  
  By default there is no CI/CD pipeline, but there is an enabled blue “Run pipeline” button: confusing.
7. Clicked the “Run pipeline” button nonetheless, and that created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job and deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert/ and https://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert/
  
  Warning: When using Pages under the general domain of a GitLab instance (gitlab.io), you cannot use HTTPS with sub-subdomains.
  
  The sites do work (see the [Archive.is http version] and [Archive.is https version]), but the HTTPS fails because wiert.me.gitlab.io does not match the SANs (Subject Alternative Names) in the certificate: *.gitlab.io, gitlab.io
For wiert.gitlab.io/wiert, try B (failed, and therefore interesting to understand why):
1. In my my groups gitlab.com/dashboard/groups, added a new group wiert
2. Added subgroups until the leaf gitlab.com/wiert/public/web/sites/gitlab.io which as URL is gitlab.com/wier1/public/web/sites/gitlab.io because user account wiert already occupies gitlab.com/wiert.
3. Under leaf group gitlab.com/wier1/public/web/sites/gitlab.io, created a new GitLab repository
4. Chose “Create from template”
5. Chose the template “Pages/Plain HTML”
6. Named the project “wiert” (with slug “wiert“) so it would appear at gitlab.com/wiert.me/public/web/sites/gitlab.io/wiert
7. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
8. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
9. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
10. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
11. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wier1.gitlab.io/public/web/sites/gitlab.io/wiert and https://wier1.gitlab.io/public/web/sites/gitlab.io/wiert.
  Bummer: again not the wiert.gitlab.io/wiert I hoped for
  The sites do work (see the [Archive.is http version] and [Archive.is https version]). The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)
12. If a user wiert exists and occupies gitlab.com/wiert, then a group named wiert cannot occupy gitlab.com/wiert, and therefore a project named wiert within that group won’t be deployed to wiert.gitlab.io/wiert.
  Maybe this can be shortened like “if there is a user wiert, then no group named wiert cannot be used to contain a project named wiert to host as wiert.gitlab.io/wiert“.
  Let’s find out!
For wiert.gitlab.io/wiert, try C (success, steps 1, 3, 4, 7 and 8 were the key ones):
1. In my user gitlab.com/wiert, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert” (with slug “wiert“) so it would appear at gitlab.com/wiert
5. The odd but cool thing is that the actual project now ended up at gitlab.com/wiert/wiert:
6. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
7. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
8. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
9. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
10. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.gitlab.io/wiert/ and https://wiert.gitlab.io/wiert/.
  Success: finally the wiert.gitlab.io/wiert I hoped for:
  
  Success: published at https://wiert.gitlab.io/wiert/
  
  The sites do work fine (see the [Archive.is http version] and [Archive.is https version]). The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)

Steps for wiert.gitlab.io

For wiert.gitlab.io, try A (failed, and therefore interesting to understand why):
1. Under leaf group gitlab.com/wiert.me/public/web/sites/gitlab.io, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert.gitlab.io” (with slug “wiert.gitlab.io“) so it would appear at gitlab.com/wiert.me/public/web/sites/gitlab.io/wiert.gitlab.io
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
7. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert.gitlab.io and https://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert.gitlab.io.
  Failure: not the wiert.gitlab.io I hoped for.
  
  The sites do work (see the [Archive.is http version] and [Archive.is https version]), but the HTTPS fails because wiert.me.gitlab.io does not match the SANs (Subject Alternative Names) in the certificate: *.gitlab.io, gitlab.io. The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)
For wiert.gitlab.io, try B (failed, and therefore interesting to understand why):
1. Under leaf group gitlab.com/wier1/public/web/sites/gitlab.io, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert.gitlab.io” (with slug “wiert.gitlab.io“) so it would appear at gitlab.com/wier1/public/web/sites/gitlab.io/wiert.gitlab.io
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
7. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wier1.gitlab.io/public/web/sites/gitlab.io/wiert.gitlab.io and https://wier1.gitlab.io/public/web/sites/gitlab.io/wiert.
  Bummer: again not the wiert.gitlab.io I hoped for
  The sites do work (see the [Archive.is http version] and [Archive.is https version]). The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)
10. Try A and B were almost identical to wiert.gitlab.io/wiert try A and B, so let’s see if the solution C for that also works for us:
For wiert.gitlab.io, try C (success, steps 1, 3, 4, 7 and 9 were the key ones)
1. In my user gitlab.com/wiert, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert.gitlab.io” (with slug “wiert.gitlab.io“) so it would appear at gitlab.com/wiert/wiert.gitlab.io.
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
7. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.gitlab.io/ and https://wiert.gitlab.io/.
  Success: finally the wiert.gitlab.io I hoped for with working sites (see the [Archive.is http version] and [Archive.is https version]).
10. Note the HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)

Steps for gitlabstatus.wiert.me

Having learned from the GitHub githubstatus.wiert.me procedure (where I had to wait a long time for the default *.wiert.me domain mapping timeout and the githubstatus.wiert.me DNS CNAME record to become effective), I started on the DNS CNAME record side which is documented at [Wayback] Custom domains and SSL/TLS certificates: Section 3. Set up DNS records for Pages: For subdomains | GitLab:

Subdomains (subdomain.example.com) require:

A DNS CNAME record pointing your subdomain to the Pages server.

A DNS TXT record to verify your domain’s ownership.

From DNS Record To

subdomain.example.com CNAME namespace.gitlab.io

_gitlab-pages-verification-code.subdomain.example.com TXT gitlab-pages-verification-code=00112233445566778899aabbccddeeff

Note that, whether it’s a user or a project website, the CNAME should point to your Pages domain (namespace.gitlab.io), without any /project-name.

From	DNS Record	To
`subdomain.example.com`	`CNAME`	`namespace.gitlab.io`
`_gitlab-pages-verification-code.subdomain.example.com`	`TXT`	`gitlab-pages-verification-code=00112233445566778899aabbccddeeff`

The value for the TXT record is only known after you created the pages project, but the value for the CNAME record is known beforehand:

From DNS Record To

gitlabstatus.wiert.me CNAME namespace.gitlab.io

From	DNS Record	To
`gitlabstatus.wiert.me`	`CNAME`	`namespace.gitlab.io`

So let’s see if I can do this in one try, with these steps:

For gitlabstatus.wiert.me, try A (success, steps 1, 3, 4, 7 and 9 were the key ones)
1. In my DNS settings of the wiert.me domain, created a CNAME record from gitlabstatus.wiert.me to namespace.gitlab.io:
  gitlabstatus.wiert.me CNAME record pointing to namespace.gitlab.io
2. Under leaf group gitlab.com/wiert.me/public/web/sites/wiert.me, created a new GitLab repository
3. Chose “Create from template”
4. Chose the template “Pages/Plain HTML”
5. Named the project “gitlabstatus.wiert.me” (with slug “gitlabstatus.wiert.me“) so it would appear at gitlab.com/wiert.me/public/web/sites/wiert.me/gitlabstatus.wiert.me
6. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
7. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
8. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
9. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
10. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.me.gitlab.io/public/web/sites/wiert.me/gitlabstatus.wiert.me and https://wiert.me.gitlab.io/public/web/sites/wiert.me/gitlabstatus.wiert.me.
  Intermediate success: working sites (see the [Archive.is http version] and [Archive.is https version]).
11. Now it is time to get the DNS CNAME record from gitlabstatus.wiert.me to namespace.gitlab.io into operation by clicking the “New Domain” button:
  
  “New Domain” button in the “Pages” settings.
12. There I filled in the correct gitlabstatus.wiert.me domain name, then pressed the “Create New Domain” button:
  
  New domain becomes gitlabstatus.wiert.me
13. Then a page appeared voiding the DNS CNAME work I already did: the documentation is clearly wrong as these are the two DNS record entries to be made as shown by gitlab.com/wiert.me/public/web/sites/wiert.me/gitlabstatus.wiert.me/pages/domains/gitlabstatus.wiert.me:
  
  Correct instructions for the DNS records to get gitlabstatus.wiert.me working
  
  Subdomains (gitlabstatus.wiert.me) require:
  - A DNS CNAME record pointing your subdomain to the Pages server.
  - A DNS TXT record to verify your domain’s ownership.
  From DNS Record To
  
  gitlabstatus.wiert.me CNAME wiert.me.gitlab.io.
  
  _gitlab-pages-verification-code.gitlabstatus.wiert.me TXT gitlab-pages-verification-code=c5619988d386b1a36c253ce05db55dbb
  Basically the whole namespace.gitlab.io part of the documentation is a placeholder for the actual namespace that belongs to the leaf group the pages project is in (in my case wiert.me).
  
  So this is the new DNS entry, for which I had to wait until the DNS TTL to time out and effectuate:
  
  New DNS gitlabstatus.wiert.me CNAME record pointing to wiert.me.gitlab.io
  
  Note that this DNS administrative interface from WordPress.com does omit the final period of the CNAME destination (officially this would be wiert.me.gitlab.io.)
14. After the CNAME DNS record, I also made the TXT DNS record:
  
  New DNS TXT record for verification of gitlabstatus.wiert.me
  
  Then I waited a little for the DNS TXT record to be saved and try the verification of the TXT record.
15. Even then, verification took some time. I had to click the refresh button a few times before verification succeeded:
  
  The DNS TXT record for gitlabstatus.wiert.me finally got verified
16. Now I could press blue “Save Changes” button below and waited for the CNAME record DNS TTL to expire so I could check the domain and – hopefully – the TLS certificate to be requested by Let’s Encrypt:
  
  After the gitlabstatus.wiert DNS TXT record got verified, I could save the domain information
17. After the old CNAME record DNS TTL expired and the new CNAME record came into effect, the domain became available as http://gitlabstatus.wiert.me/:
  
  Waiting for gitlabstatus.wiert.me to become active
18. After verification, the “Domains (1)” bit changed from this:
  
  Domain gitlabstatus.wiert.me information before verification
  
  to this:
  
  Domain gitlabstatus.wiert.me information after verification
19. In the mean time, also the TLS certificate got issued by Let’s Encrypt, so the final sites now both worked: http://gitlabstatus.wiert.me/ and https://gitlabstatus.wiert.me/.
20. Success: finally the gitlabstatus.wiert.me I hoped for with working sites (see the [Archive.is http version] and [Archive.is https version] for the wiert.me domain, and [Archive.is http version] and [Archive.is https version] for the wiert.me domain).
21. Note the HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)

From	DNS Record	To
`gitlabstatus.wiert.me`	`CNAME`	`wiert.me.gitlab.io.`
`_gitlab-pages-verification-code.gitlabstatus.wiert.me`	`TXT`	`gitlab-pages-verification-code=c5619988d386b1a36c253ce05db55dbb`

In retrospect, this could have been shorter when I had done the DNS part later, which is contrary to how to do this with GitHub.

Conclusion

The conclusion seems this:

Gitlab Page repositories to be published as or under wiert.gitlab.io need to reside directly under user wiert. Having them reside under a different group like wiert or wiert.me won’t work.

Or in more generic terms:

When creating pages as user.gitlab.io you have to put your pages projects directly under your user account gitlab.com/user.

Putting them under groups or leaf groups fails, no matter if the (leaf) group is named user or otherwise.

In addition, you can add custom domains to any Gitlab repository (even one that never stated out as a GitLab Pages repository). It will work as soon as the domain DNS mapping is setup through both a CNAME mapping record and TXT verification record.

The steps for this in your GitLab repository are:

Ensure you have a valid .gitlab-ci.yml file at the root of your repository; I used the [Wayback/Archive.is] one from [Wayback/Archive] GitLab Pages examples / plain-html · GitLab as my site is purely static
Ensure you have a valid index.html file in the public directory of your repository, similar to [Wayback/Archive] GitLab Pages examples / plain-html · GitLab
When both 1. and 2. are committed in your repository at GitLab, then it will automatically be deployed to a docker container on gitlab.io, which allows the outside world to visit your GitHub Pages sie, and the Let’s Encrypt Certificate to be generated (and prevents this error: [Wayback/Archive] GitLab Pages integration with Let’s Encrypt | GitLab: “Something went wrong while obtaining the Let’s Encrypt certificate”).
Under “Settings” -> “Pages”, add a new domain name to the repository: now it automatically becomes a GitLab Pages repository.
When adding the domain, the settings page will show both a DNS CNAME record and DNS TXT record; ensure both are applied on your primary DNS name server and replicated to all authoritative DNS name servers.
Save the new page.
Check if the page is available on the new domain you added.
Optionally under “Settings” -> “Pages” enable the “Force HTTPS (requires valid certificates)” option and save.

TLS information

Note: I saved the TLS information – including certificates here:

[Wayback] certcheckerapp.com/home?hostname=wiert.me.gitlab.io&hideResult=false
- [Wayback] Wildcard GitLab certificate with serial number 5B0C885BD0E0A1A52AD5C29D for *.gitlab.io, gitlab.io.
- [Wayback] Certificate chain
[Wayback] certcheckerapp.com/home?hostname=wier1.gitlab.io&hideResult=false
- [Wayback] Wildcard GitLab certificate with serial number 5B0C885BD0E0A1A52AD5C29D for *.gitlab.io, gitlab.io.
- [Wayback] Certificate chain
[Wayback] certcheckerapp.com/home?hostname=wiert.gitlab.io&hideResult=false
- [Wayback/Archive.is] Wildcard GitLab certificate with serial number 5B0C885BD0E0A1A52AD5C29D for *.gitlab.io, gitlab.io.
- [Wayback] Certificate chain
[Wayback] certcheckerapp.com/home?hostname=gitlabstatus.wiert.me&hideResult=false
- [Wayback/Archive.is] Regular domain certificate with serial number 3380904328FD4633E6CF27FE9B7D5BE25AE for gitlabstatus.wiert.me.
- [Wayback/Archive.is] Let’s Encrypt issuer certificate with serial number 912B084ACF0C18A753F6D62E25A75F5A for R3.
- [Wayback/Archive.is] X1 root certificate with serial number 4001772137D4E942B8EE76AA3C640AB7 for ISRG Root X1.
- [Wayback] Certificate chain

More about the Let’s Encrypt certificates at [Wayback] Chain of Trust – Let’s Encrypt:

–jeroen

Read the rest of this entry »

Posted in Cloud, Communications Development, Development, DNS, Encryption, GitLab, Hosting, HTML, HTTPS/TLS security, Infrastructure, Internet, Internet protocol suite, Let's Encrypt (letsencrypt/certbot), Power User, Software Development, Source Code Management, TCP, TLS, Web Development | Leave a Comment »

NPoole/BeanCounter

Posted by jpluimers on 2022/05/04

[Wayback/Archive] NPoole/BeanCounter

A Simple, Affordable, Counter for Cut Tape and Partial Reels.

Soon it should become available on [Wayback/Archive] BeanCounter | Crowd Supply

Via [Wayback/Archive] 🌟Cyber City Circuits🌟 on Twitter: “Get hyped. “.

–jeroen

Posted in Development, Hardware Development, LifeHacker, Power User, Soldering | Leave a Comment »

capitaltg/thea: Certificate Checker and https://certchecker.app site

Posted by jpluimers on 2022/05/03

[Wayback/Archive.is] capitaltg/thea: Certificate Checker

Certificate Checker provides an easy-to-use solution to check certificates, certificate chains, and TLS configurations. To run Certificate Checker for publicly-accessible web sites you can go to: https://certchecker.app and enter in there a URL to check.

Users can easily run Certificate Checker in an internal network to validate or troubleshoot their TLS configuration. To run it on a local network you can run the Docker image as described below. You can also build the application and deploy it on an existing server.

It runs on [Wayback/Archive.is] Certificate Checker.

I used it to check various certificates and chains, including those for my GitHub Pages explained last week in Setting up a GitHub project so it is served over https as a custom subdomain.

–jeroen

Posted in Communications Development, Development, Encryption, HTTPS/TLS security, Internet protocol suite, Let's Encrypt (letsencrypt/certbot), Power User, Security, Software Development, TCP, TLS, Web Development | Leave a Comment »

Converting an existing XP machine to a VMware ESXi Virtual Machine and having boot issues?

Posted by jpluimers on 2022/05/02

A while ago I wrote about Stop 0x0000007B after converting an existing XP machine to a Virtual Machine (ESXi, Hyper-V, or other).

After this, the machine still had boot issues (a grey or black screen after boot, unless booted via Grub from a rescue CD).

The solution in retrospect was simple, but I only figured out after the fact what the solution had done.

Of course this gave me a facepalm moment, as back in the days, this was exactly the warning I gave everyone when installing Windows XP on ESXi anyway: use a SCSI buslogic based virtual disk, not an IDE or SATA virtual disk.

The reason is that Windows XP does not like the IDE/SATA disk that VMware provides. Windows Vista and up are less of a problem.

This is indeed what my practical solution did:

VMware Converter 4.x creates a VM with an IDE/SATA disk (as it cannot talk to the more recent ESXi versions at all because of API changes)
VMware Converter 6.x creates a VM with a buslogic SCSI base disk (and it can create it directly on your ESXi rig, though it will use a directory in the root of your data store, even if you prefer it somewhere deeper in the directory tree)

References:

[Wayback] P2V Windows XP – VMware Technology Network VMTN (showing VMware Converter 6.x steps)
[Wayback] P2V Windows XP Won’t Boot – VMware Technology Network VMTN

…

did you create a IDE-based VM ?

That will not work – though it is offered as an option. Converter uses a bluff here

…

try again first – use Buslogic when asked for the controller.

If that does not work either try Converter 3.0.3 next

if that still fails post boot.ini and a screenshot of diskmanagement of the XP-source

…

SCSI was the answer.

Thanks.

…

–jeroen

Posted in ESXi6, ESXi6.5, ESXi6.7, Hardware, Power User, SAS/SATA, SCSI, Virtualization, VMware, VMware Converter, VMware ESXi, Windows, Windows XP | Leave a Comment »

How to survive cancer: an inspiring story by Désirée Hairwassers

Posted by jpluimers on 2022/04/29

Today is my birthday. I am turning 53 today. But when writing this I’m not sure I am what we Dutch call “schoon”. It is a Dutch euphemism that I dislike, but still accidentally use. The thing is that one never knows for sure to be really clean from he signs of cancer metastases.

While writing this post, I’m in a melancholic mood during a period of depression/burnout after all the treatments. I am reflecting on if and how I survived the metastasised rectum cancer and lived through all other stressful things that started somewhere early 2017.

So I was glad to find the tweet below on the edge of spring that inspired me, I originally made me draft this post as being titled

“Surviving cancer is not a fight or a battle, it is about having luck or misfortune”

It was a (now by posting this link) pointer back to Having cancer is not a fight or a battle, it is about having luck or misfortune.

But it doesn’t do the artwork of Désirée Hairwassers justice, so here is her tweet:

[Wayback/Archive] Dees on Twitter: “Het lijkt mij ook een gepast moment om jullie mijn boek te presenteren. In het Engels, want gericht op de hele wereld. Dun boek. Dat moet een bestseller worden….. “

Translated: “I also think it is an appropriate time to present my book to you. In English, because aimed at the whole world. Thin book. That should be a bestseller”

And her video about “How to survive cancer: The inspirational journey of Désirée Hairwassers” showing the book. A very focused book (if it does not show, click on her above tweet to see it):

Read the rest of this entry »

Posted in About, Awareness, Cancer, LifeHacker, Personal, Power User, Rectum cancer | Tagged: borstkanker | Leave a Comment »

virtualization – Convert a hard-drive into a VMWare machine – Server Fault

Posted by jpluimers on 2022/04/29

Sometimes machines die without one having had the chance of doing a proper bootable file-system backup instead of a file-by-file-backup.

You can still P2V these machines (convert them from physical to virtual), but it is a lot more pain as you have to try to grab any installation keys for them and create a compatible virtual machine configuration by hand like I did in P2V of an existing XP machine to Hyper-V to have an emergency fallback when retiring old XP physical machines.

The below linked answer (with steps) uses Symantec Backup Exec System Recovery (now back in the hands of Veritas again as Backup Exec) to make part of this process towards VMware ESXi less tedious: [Wayback] virtualization – Convert a hard-drive into a VMWare machine – Server Fault (thanks [Wayback] Mark Booth and [Wayback] Dave M)

Doing this might require you to find old Windows XP media. Those are in the Internet Archive (often slower, but has the file hashes too) and The Eye (much faster from where I live in Europe); Internet Archive examples are for English, though other languages are present as well:

Internet Archive: Windows XP Professional SP3 x86 : Microsoft : Free Download, Borrow, and Streaming : Internet Archive
Internet Archive: [MSDN] Windows XP Professional SP3 x86 (32 bit) RETAIL English : Microsoft Corporation : Free Download, Borrow, and Streaming : Internet Archive
Internet Archive: [MSDN] Windows XP Professional SP3 x86 (32 bit) VL (volume) English : Microsoft Corporation : Free Download, Borrow, and Streaming : Internet Archive
[Wayback] Index of /public/MSDN/Windows XP/

The Eye is a website dedicated towards archiving and serving publicly available information. #opendirectory #archive #digitalhistory

Got the Internet Archive tip from [Wayback/Archive.is] Where can I download an official Windows XP ISO? I have a license key if that helps? : windows, found the correct filename there, then downloaded the [Wayback] The Eye.

–jeroen

Posted in Hyper-V, Power User, Virtualization, VMware, VMware ESXi, Windows | Leave a Comment »

Setting up a GitHub project so it is served over https as a github.io and a custom subdomain

Posted by jpluimers on 2022/04/27

Some links that helped me getting this working:

Read the rest of this entry »

Posted in Cloud, Cloudflare, Communications Development, Development, Encryption, GitHub, HTML, HTTP, HTTPS/TLS security, Infrastructure, Internet protocol suite, Let's Encrypt (letsencrypt/certbot), Power User, Security, Software Development, Source Code Management, TCP, TLS, Web Development | Leave a Comment »

GitHub – bbbradsmith/flompy: DOS floppy disk dumper

Posted by jpluimers on 2022/04/26

Need one day when archiving old floppies: [WayBack] GitHub – bbbradsmith/flompy: DOS floppy disk dumper

Via: [WayBack] Brad Smith on Twitter: “So I wrote a floppy disk dumper program for DOS. I dunno if this is really a very useful thing, but it’s open-source at least! 💾⚡🖥 “

Full thread at [WayBack] Thread by @bbbradsmith: “Hrm… why doesn’t the floppy controller status register have its non-DMA bit set, even though I’ve used a specify command to set it… and […]”:

Read the rest of this entry »

Posted in Development, History, MS-DOS, Power User, Software Development | Leave a Comment »

Some links on removing colon tissue with Endoscopic Full Thickness Resection (EFTR)

Posted by jpluimers on 2022/04/25

Since they are likely to perform an FTR/EFTR procedure to remove a ~2.5cm sized polyp growing inside the colon on top of the LAR (Lower Anterior Resection) surgical suture line, below are some links, partially in Dutch, partly in English.

Searches

Since they are related to my LAR-syndrome symptoms:

Read the rest of this entry »

Posted in About, Health, LifeHacker, Personal, Power User | Leave a Comment »

« Previous Entries

Next Entries »

	Jeroen Wiert Pluimer… on Does Odido (the old T-Mobile N…
	Lars Fosdal on Security alarm provider Woonve…
	Thomas Mueller on Question got closed in May 202…
	Thaddy de Koning on Formulier voor bewindvoerders…
	Thaddy de Koning on Formulier voor bewindvoerders…

The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

Twitter Updates

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘Power User’ Category