Jump to content











Photo

Unresponsive after loading Windows files

windows mouse cursor keyboard

  • Please log in to reply
3 replies to this topic

#1 gerster43

gerster43
  • Members
  • 3 posts
  •  
    Canada

Posted A week ago

Hey there, I posted this in the bug report thread but then realized its probably not a bug.  Just some strange strange issue that nobody else seems to be having.  I'm wondering if anyone could shed some light on what's going on for me, because I'm absolutely stumped.

 

Hey everyone,

 

Please forgive me if I'm posting in the wrong area.  I've struggled to find support for the very specific issue I'm having;

 

I should firstly say I'm quite confident this isn't an issue with Tiny PXE itself, as I'm having the exact same problem when using a similar but different program called Serva.

 

My goal is to install Windows 10 onto a newly built machine via network boot.  Both Tiny PXE and Serva appear to run flawlessly.  But consistently, after loading the windows files, as soon as I reach any point in the installation which requires input (in Tiny PXE's case, as soon as I reach the step to enter the shared folder path) my machine simply locks up and keyboard/mouse movements aren't registered.  It's consistently about 0.5 seconds after my first input.  So I might be able to enter a couple characters in the text box, but that's it.  Sometimes my mouse appears to completely disconnect (ie. power light goes off) and sometimes it stays powered on.

 

The obvious first thought would be that it's a hardware issue with the mouse or keyboard, but they in fact work flawlessly in every other machine I've tried.  They also work flawlessly in the BIOS for long periods of time.  I've also tried navigating with the mouse unplugged, but inputs from the keyboard still aren't registered (after about 0.5 sec from initial input).  I've tried unplugging the keyboard directly after making necessary inputs, and the problem persists.

 

I've tried every USB and combination of USB ports on the machine, same issue.

 

I've tried many different Windows 10 ISOs including the freshest one directly from Microsoft's media creation tool, same issue.

 

Firewall is off, and in/outgoing connections for Tiny PXE (and Serva) are explicitly allowed in defender.

 

I've contacted Gigabyte support thinking it may be some strange issue with my H110m.2 rev. 1 board.  They are as stumped as I am.

 

Is there anyone here who might have any idea as to what's going on?  Its been days of trial and error and tweaks and headaches but I'd really like to get this working.

 

For the record, Tiny PXE is soooo much smoother and simpler than Serva.  I'm glad I found this program.  Just wish I could solve this very strange issue!

 

Thanks.



#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14955 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

It is "strange".

 

Did you try to use a "local" install source (i.e. DVD or USB stick) as opposed to the PXE one?

 

I.e. is the issue keyboard and mouse confilcting *somehow* with the install/loaded PE or are they conflicting with network activity/network card?

 

Semi-random idea, but have you tried a fully unattended setup?

 

*like*:

https://www.tenforum...ndows-10-a.html

 

I don't know if it is actually a good idea, since making an unattended install is - generally speaking - complex.

 

And anyway - not to put you down in any way  :) - is the matter actually worth the time that will be needed to (hopefully) find and resolve the cause/issue?

 

I mean, if you have to install several of these machines or if you are doing only for the fun of it, it is OK, if you only need to install on that single machine, get a local media, install the stupid Windows 10 and call it a day ;)

 

:duff:

Wonko



#3 gerster43

gerster43
  • Members
  • 3 posts
  •  
    Canada

Posted 3 days ago

Hey there. I figured out my issue was because of a faulty RAM stick. Replaced the stick and everything ran flawlessly. Problem solved!

#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14955 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 2 days ago

Hey there. I figured out my issue was because of a faulty RAM stick. Replaced the stick and everything ran flawlessly. Problem solved!


Happy it worked :) and thanks for letting us know/finalizing the thread.

:duff:
Wonko




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users