Ok I updated my downloads following this guide. However when I go to \Downloads\AppYGS\Network\Remote Connect\UltraVNC-Plugin it still shows as v23 and not v24. Am I doing something wrong?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - JohnB175
ChrisR, I did exactly what you suggested and it worked for Grub4DOS. On another note, under OtherOSY\Multi-WIM if I picked WinBCD-Menu rather than Gru4DOS-Menu and build the project, it doesn't give me any time to select the from the BCD menu. I even changed the timeout to 15 seconds under Multi-WIM but it just immediately starts booting Win10PESE. Is there something I am missing? Thanks again for all the help.
I've recently moved from Win7PESE with multi-wim to Win10PESE. I added the \downloads\OtherOSY\Multi-WIM\multi-wim - plugin and added my old Win7PESE wims for legacy purposes. I noticed I cannot added the Menu Options on the first screen that comes up which I think is a grub4dos screen. I have to select WIN10PESE and then that brings up another menu where I can select my old wims. When configuring the plugin if I select Grub4dos-menu from the multi-wim plugin it tells me it's only available for Windows7 SP0/SP1. I noticed on my old Win7PESE I have multiple BOOTMGR's in the root of the flash drive (BOOTMGR1, BOOTMGR2, etc.) and in the menu.lst they were listed like this:
title Win7PESE with Acronis Echo
title Win7PE_SE with Acronis 2013
I must be missing something. Any help would be greatly appreciated.
Yep, that was it. Before going the RealVNC route I played around with the various UltraVNC builds. I got the one under \Downloads\AppsGS\Network\Remote Connect\UltraVNC to work with a blank password by editing the ultravnc.ini to include "AuthRequired=0" and removing the lines "passwd=" and "passwd2=" in case anyone wants to do this. By the way, what's the difference between AppsGS, AppY and AppYGS? There seems to be some overlap in the plugins.
I checked \Downloads\AppYGS but there was not Remote Connect. I went to \Utils\Downloads and clicked the green arrow for download plugin and then the large Update \Downloads\ button but this did not add the Remote Connect to \Downloads\AppYGS. Am I missing something? I've attached a screenshot showing what I am seeing.
I am moving from Win7PESE to Win10PESE and am having some difficulty getting my UltraVNC plugin to work correctly. In Win7PESE it would wait 90 seconds after boot and then launch with a blank password. I can't seem to even get it to copy the files to the target folder. I am attaching the script it the hopes that someone can take a look at it. Thanks for all your help.
« on: March 12, 2015, 12:07:30 PM »
I started a fresh Win8PESE project and the penetwork with the same settings works perfectly. The penetwork_after.cmd executes and maps the drive. It appears to be something with the Win8.1PESE. Anyone have any ideas?
« on: March 11, 2015, 09:54:58 AM »
As a test, I started a whole new Win8.1PESE project on another pc with no options changed, nothing added, nothing removed. I set the Static IP address profile to be the default. I built the project and when I boot off the flash drive it pulls a dynamic address. It is definitely not using the Static IP Address profile as the IP would be set to 192.168.0.200. that I have it set to in the PeNetwork editor. Is this a known issue? Can anyone else confirm that this is happening to them? I don't know where else to go from here.
« on: March 09, 2015, 03:14:12 PM »
Ok, so I turned Components/Network back on, set the default profile to Static IP with no special commands and rebuilt using the recommended ISO. I wanted to see if it would assign the default IP of 192.168.0.200 When I boot from the flash drive the network comes up as normal but it does not assign the 192.168.0.200 address that is set in the static IP profile. It's almost seems like it's ignoring the profiles. I've double checked everything and can't seem to figure this one out. On a side note, I am including screenshot attachments of when I was using the dynamic profile with the penetwork_after.cmd to make sure everything looks correct.
« on: March 09, 2015, 12:04:30 PM »
Well, if I load PEnetwork once it's booted, I can change b/t static which sets the IP to 192.168.0.200 and dynamic which of course just pulls a random IP. It's just that the penetwork_after.cmd is not getting executed when the dynamic profile is applied. I am using a final x86 build of Windows 8.1 (SW_DVD5_Win_Pro_8.1_32BIT_English_MLF_X18-96671.ISO). I will download the one from the main project list called "Windows 8.1 Update Enterprise Evaluation ISO 32-bit (x86) version REFRESH 9600.17050" just to test if you think it will help and report back.
« on: March 09, 2015, 10:58:46 AM »
Sure thing. Like I said, the script works in Win7PESE and works in Win8.1PESE if I double click it, so as far as I can see the script is fine. It attempts to ping the a certain IP, once that IP is reachable, it exits the loop and maps the drive. I removed the username and password from the script for security.
I've been using Win7PESE for some time now. I just switched to Win8.1PESE. I have everything working except my script which maps a network drive. From the builder under Components/PeNetwork, I made sure that "Use profiles on network startup is selected, and that my cmd file is in %GlobalTemplates%\PENetwork_Include. I then clicked start editor. I have the default profile set to "Dynamic IP Address" and under that profile I have CMD's after startup set to x:\windows\system32\penetwork_after.cmd. My script is in the file penetwork_after.cmd. I build the project and when I boot from the USB I can see the penetwork_after.cmd file in the x:\windows\system32 folder. However, the file never gets executed. If I go an manually double click it, it maps the drive successfully. Any ideas on what I am missing here? I compared my old Win7PESE to the new Win8.1PESE and everything looks correct. I have attached a copy of my Penetwork.ini
I've noticed with the latest release of WinBuilder (v49), that some machines will not boot off the created usb flash drive. So far I've had two machines (one was an Intel D945GCLF and the other was a core2 duo board that I can't recall the model number) that will see the flash drive in the BIOS but when told to explicitly boot off the drive it simply boots into the OS on the hard drive. I am using HPUSB for the formatting tool and GrubInstall for the MBR Tool. I still had a flash drive that I had created with a 2011 version of WinBuilder and that one worked on both machines. Any ideas? On a side note, I tested this method (first post) of using ntdetect, ntldr, boot.ini which calls grldr and it booted on one of the problem machines (the other machine I no longer had access to). Any ideas why this would work?
« on: September 03, 2013, 05:29:12 AM »
Awesome. Thanks for the help from both 2aCD and you. I'm glad to pitch in any way I can. If I see any other issues, I will let ya'll know.
« on: September 03, 2013, 03:24:03 AM »
Looks like your updated version worked on the problem machine ChrisR. Should I continue to use your version or the test3 version from 2aCD? Is your version going to be the final version? Both seem to work.
« on: September 02, 2013, 05:32:47 AM »
Ok, I will test this out first thing tomorrow morning when I get to the office and have access to the test machine. I'll report back and let you know.
« on: September 01, 2013, 03:26:45 AM »
Where would I download your updated script out ChrisR?
« on: August 30, 2013, 03:21:59 PM »
I'm not going to be back in my office until Tuesday of next week so will not have access to that test machine until then. I did try on my test machine with a hard drive plugged in with the original script and it would not change the drive mappings. It simply made my flash drive E or whatever was the first letter available. 2aCD did generate a working script for me this afternoon (08-30-2013). It's v.17 test3. You can find it here (reboot.pro/index.php?app=core&module=attach§ion=attach&attach_id=14515_). Maybe you could take a look at what he did in that test3 script. Do you still want me to test with the script you have posted above next week?
« on: August 30, 2013, 09:09:55 AM »
I've been trying to figure this problem out with 2aCD over at reboot.pro. Despite out efforts we cannot get the flash drive to change it's drive letter to Y when it boots on some hardware. In my test machine which has no hard drive it always shows the flash drive as drive C:. You can read all that we have tried here (reboot.pro/topic/15694-acronis-backup-recovery-11-in-win7pe/page-4). It starts at post #84. It won't let me post links so just copy/past. 2aCD recommended to post here and maybe ChrisR could help to figure this out.