draiser.net Report : Visit Site

Technical data of the draiser.net

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host draiser.net. Currently, hosted in Italy and its service provider is IUNET BNET .

otaconline.org 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.25 (Debian) containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

draiser's techblog let's get technical menu skip to content techblog about me portfolio stories (pl) privacy policy diy handheld console – version 2 2 replies although it was great to work on supergamepi-based diy handheld console project, the device wasn’t that much fun to actually use and play . i wasn’t really thinking about it when i was building it – i assumed that fun from constructing & hacking around would be rewarding enough – yet i got nervous more than once when i actually tried to play longer than for a few minutes and there was always some inconvenience. what went wrong? problem 1 was that my soldering work wasn’t perfect and i was having connection shortages which caused gamepad buttons not working or – actually worse – working when they shouldn’t. with a few iterations of desoldering and resoldering, i’ve managed to actually fix that issue. problem 2 was that after so many deconstructions and reconstructions of gamepi as project needed, screw holders eventually gave up. i’ve used super glue to fix them and it worked for a while, but not long enough. still, that could be fixed, in worst scenario by reprinting gamepi case (which was a bit pricey). problem 3 was the one which eventually led me to go back to drawing board and redo the whole pi-based handheld console project. even though buttons worked, they haven’t really worked well . they were incosistent in tactile feeling plus amount of force needed to press each button differed. this wouldn’t be a problem in many projects – some house applications or soundboxes and such – but in gaming? it’s instant death because of jump which didn’t happen, loss of trial in mario kart, shooting failure in worst moment, even in turn-based jrpgs it was very irritating. handheld v2 – design! i decided to completely change aproach and build modular system which would allow to swap components easily and to use already working gamepad part. of course, it’s still possible to use many other options: one can print 3d case which enables to hold snes-like controller whole , gut wii u “tablet” and insert pi there or use smartphone bluetooth gamepad-case. i’ve decided to go with last option, as bt gamepads are generally nicely recognized by raspberry pi/retropie and their construction should enable flexibility in rebuilding later on. i didn’t like any option provided by popular company ipega , but found very promising photos & spec of joypad flydigiwee . it seemed rather unknown/untested in non-china world, yet i’ve liked it so much that i figured it’s worth trying out. eventually i’ve had to order it twice and waited almost half a year for it (yeah…), but bad luck stopped there. building parts in first version of handheld, i’ve used cheap 5″ gps navigation screen plus not so cheap controller driver by adafruit . initially i wanted to use that for v2 as well, but unfortunately plastic holder for controller tape broke and i couldn’t find anywhere reasonably priced replacement. while thinking about about 3d printed replacement part, i eventually ordered another cheap 5″ screen with hdmi , designed for raspberry pi as it was accessible in my country. there was an iussue with placement of gpio block used for touch which i didn’t need and microusb power port was put at right side of the screen – it collided with gamepad holder – so i removed both of them using as low force as i could and with help of my friend ingvar i soldered 5v power plus ground instead. those changes made it really easy to use raspberry pi’s two gpio ports to give power to the screen. success ! holding it together while gamepad holder matched very well with screen (ok, after making stupid “backlight switch” smaller), i needed a way to hold rpi in place. once more, first idea was to print 3d case for whole construction, but that would break modular approach so i decided that the simplest way is the best way – i ordered beautiful blue/clear case for rpi (with access to gpio of course) and mounted it to gamepad with… cable holders. i can’t imagine more modular approach. ;) power over 9000! while screen was nicely powered by rpi gpio ports, pi itself needed power. i’ve done another quick research and eventually reused powerbank which i bought for v1 . it has 6000 mah capacity which is enough for a few hours of work (haven’t measured it exactly so it’s approximation ) and 2.1a usb exit which is optimum for rpi 2 b. potentially it could be not enough for rpi 3, but i use pi i have ( duh ) and pi 3, although has more power, has also higher needs – not only powerwise, but also regarding cooling necessarry for proper running. going back to powerbank – it’s quite heavy for such a small project (160g), yet comparing to other ones (eg. aluminium xiaomi one which i use with smartphone & tablet) i can’t find better option which would still have nice capacity and amper outage. also, it’s about the same size as rpi in case which is great, because if it was any longer it would be not comfortable to hold console in palms ( which kinda is a goal here ). as you may imagine, i’ve used cable holders to put it all together. glorious! :) cables?! hdmi powered screen and longer (comparing to standard usecase) space between screen and rpi caused that i couldn’t use compact hdmi connector to hold it together. in result i have to to use standard hdmi cable. well, perhaps not standard, because i’ve used as short one as i could’ve find – but it was still not perfect. then my friend dźwiedziu came with suggestion to… make it tangled like an old stationary phone cord. perhaps it was crazy, but worked! when you can’t hide it, make it intentionally visible. cool! software this hasn’t changed from version 1 – i still use retropie and it’s a great piece of work. it’s configured to support a lot of emulators, custom ports and such. retroarch is running in backend which enables automatic configuration and mapping, is easy to use and has great emulationstation ui. only competition for retropie is recalbox – designed for ease of use whuch leads to having less configuration options available. and i always prefer to have as vast selection as possible. snes, gb&gba, psx emulation works great; n64 is so-so. all ports i’ve tested so far work great – doom, duke nukem 3d, quake 1 & 3(!), minecraft pi edition (but not with gamepad), stratagus for warcraft ii (same), cave story and more. please let’s not discuss emulation legality here . i can also turn in into full lxde/pixel desktop, but it’s more of gimmick than real usecase. after all this 5″ screen has only 800×400 resolution. first version, which used custom-build switches connected to arduino pro micro hacked around to work like keyboard, was great because it allowed to use gamepad in places where it isn’t available normally – eg. for dosbox games. i lost that functionality in handheld v2 unfortunately. while dosbox has nice mapper for assigning joysticks/gamepads buttons to keyboard keys, it’s not working properly with my flydigiwee – all buttons, except arrows, are reported as one. too bad. i’ve tried to register gamepad as keyboard+mouse using xboxdrv driver, but it hasn’t worked in dosbox and stratagus as well. maybe there will be something better in future. what does the future hold? project is cool and i’m already using it a lot, but it’s a bit too heavy to my liking. it’s caused by powerbank which is the first thing i’d like to replace (maybe aside of “speakers”) – when they’ll create something lighter with more capacity and outage. other than that, i’m satisfied. i may change pi 2 to another module in the future, but probably not to pi 3 – its power is not that great and its needs are much higher. let’s play! this entry was posted in diy , gaming , mobile on 20 december 2017 by draiser . why do i use linux? leave a reply customization it’s system which i can fully make look & behave like i want. i prefer dark themes – no problem, tons of those to selects. my fonts, image settings, etc are shared system-wi

URL analysis for draiser.net

http://www.draiser.net/#content
retropie.org.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: DRAISER.NET
Registry Domain ID: 1598669608_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.dreamhost.com
Registrar URL: http://www.DreamHost.com
Updated Date: 2017-05-24T07:28:40Z
Creation Date: 2010-05-23T17:01:25Z
Registry Expiry Date: 2018-05-23T17:01:25Z
Registrar: DreamHost, LLC
Registrar IANA ID: 431
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: ok https://icann.org/epp#ok
Name Server: NS1.DREAMHOST.COM
Name Server: NS2.DREAMHOST.COM
Name Server: NS3.DREAMHOST.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-12-13T22:31:16Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR DreamHost, LLC

SERVERS

  SERVER net.whois-servers.net

  ARGS domain =draiser.net

  PORT 43

  TYPE domain

DOMAIN

  NAME draiser.net

  CHANGED 2017-05-24

  CREATED 2010-05-23

STATUS
ok https://icann.org/epp#ok

NSERVER

  NS1.DREAMHOST.COM 64.90.62.230

  NS2.DREAMHOST.COM 208.97.182.10

  NS3.DREAMHOST.COM 66.33.205.230

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .