Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Online patch tool - Domain expired #115

Closed
hpingel opened this issue May 29, 2021 · 11 comments
Closed

Online patch tool - Domain expired #115

hpingel opened this issue May 29, 2021 · 11 comments

Comments

@hpingel
Copy link

hpingel commented May 29, 2021

It looks like the domain has expired and the online patch tool is not available. Thank you for your good work!

@ian5142
Copy link

ian5142 commented May 29, 2021

You mean this domain: http://simeonpilgrim.com/nikon-patch/nikon-patch.html or the Nikon Hacker forum, both are up for me.

@hpingel
Copy link
Author

hpingel commented May 29, 2021

I checked on a different computer and there I get the right website I suppose. On my Android phone I get this - see screenshot -
Screenshot_20210529_173338
in Chrome and in Firefox browser

Is this a fake add overlaying the tool's page?

@simeonpilgrim
Copy link
Owner

The domain, is still valid for a few more years, but I have lost access to the hosting management tool.
Cheers for the warning/headup.

Have started talking with hosting provider.

@simeonpilgrim
Copy link
Owner

for now the patching site can be reached at this cloudfront address:

https://dyk3v11u6y5ii.cloudfront.net/nikon-patch/nikon-patch.html

working on getting the domain and the rest of the site migrated.

@stevegoossens
Copy link

stevegoossens commented May 30, 2021

I also wondered what was happening with your site and just assumed "hosting issues" and built the tool site/page and hosted it at https://www.amazinggoose.com/nikon-patch/nikon-patch.html before thinking to check the repo issues and finding this issue 😄

So, good news is that your site build instructions were good enough for me to build on Mac, with a few tiny bits (the .cmd files) easily being translated to the corresponding commands that work on a non-Windows shell.

(Note: I "mirrored" your patch tool as I refer to it in my YouTube video that shows me going through the process including finding old firmware)

@simeonpilgrim
Copy link
Owner

So, good news is that your site build instructions were good enough for me to build on Mac, with a few tiny bits (the .cmd files) easily being translated to the corresponding commands that work on a non-Windows shell.

Glad that .cmd files acted as the intended bread crumbs for others to follow. Even if you are gluten free.

@stevegoossens
Copy link

Haha, yeah they worked... I was too lazy to walk upstairs to use my Windows laptop and used my (work) MacBook instead.

@stevegoossens
Copy link

I'm sure there are many guides on using your Nikon Patch tool, but I think I struggled a bit to find the original firmware download and initially missed the bit about renaming the patched firmware. That's why I bothered to do a screen capture when attempting it, to present as a rambling unedited example of someone doing it for the first time.

I've just finished writing a guide to using the tool on my site at https://www.amazinggoose.com/nikon-firmware-patch/ and to make it something useful to the community, I found all the download links for the Nikon original firmware and included them in the article.

Maybe this will be useful to someone :)

@simeonpilgrim
Copy link
Owner

nice work on providing links. we avoided that as at the time we were working on "current" firmware, and we want to not provide any files that violated copyright. Thus why the patch tool does the work on the client side via (originally silverlight) webassembly

@stevegoossens
Copy link

That old chestnut eh. Yeah I did something similar for an abandoned PC game (Hawken) that needed a backend for login and user profiles/inventory.

I remade the backend API and then we provided a download of the unmodified game client, and instructions on how to edit the client config (just a text file) for the backend URL.

@simeonpilgrim
Copy link
Owner

site is up and running again, thanks again for the heads-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants