Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sanhook takes a long time
2017-12-06, 17:02 (This post was last modified: 2017-12-06 17:11 by NiKiZe.)
Post: #5
RE: Sanhook takes a long time
(2017-12-06 16:14)zoup Wrote:  
(2017-12-06 15:35)NiKiZe Wrote:  
(2017-12-06 16:12)zoup Wrote:  sanboot --drive 0x81 --no-describe http://192.168.65.3/Images/ISOs/win7.iso

now problem is, windows boot manager starts and returns error 0xc0000225 (https://neosmart.net/wiki/0xc0000225/)
To boot windows installation from iPXE it is recommended to use wimboot instead.

Thanks, i just started it as a new thread, and delete the post here.

You are using the exact same script except for the last part - so merging the two threads (again) since it is as far as I can see the _SAME_

to help you first you need to help us by providing and testing the things that are asked.

(2017-12-06 16:14)zoup Wrote:  
(2017-12-06 15:31)NiKiZe Wrote:  Above you said it hangs first with the exact same script, try to solve or explain that issue first instead of posting multiple threads please.


Yes, here i'm saying hooking taking a long time, not related to not being able to boot.
But again it is the exact same script, with the exact same target. Saying they are not related in this case makes little sense, as such i regard these posts as duplicates.

Use GitHub Discussions
VRAM bin
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Sanhook takes a long time - zoup - 2017-12-05, 15:52
RE: Sanhook takes a long time - NiKiZe - 2017-12-06 17:02
RE: Sanhook takes a long time - zoup - 2017-12-07, 10:43
Sanhook And Iso HTTP boot - zoup - 2017-12-06, 16:12



User(s) browsing this thread: 1 Guest(s)