Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


solutionone

Member
  • Content Count

    28
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About solutionone

  1. wimmaster can be found at this link http://www.boot-land.net/forums/index.php?...amp;#entry21075
  2. Hi Geezery, sorry its been so long since I last replied, I have tried out version 0.70 beta 4, I cannot get the Install option working, it starts the diskpart, and then crashes out somewhere after the disk is wiped. also is the option to choose which disk/partition to install to going to make this version?
  3. Hi Geezery, I just finished work for the day so I can't test the new beta right now, but I will download it and test it tomorrow and get back to you. regards
  4. Hi Geezery, sorry it has been so long since I last posted, I've been flat out at work. I have tested beta 0.070 and picked up the following bugs/suggestions. 1. Map network drive. once clicking the button from the main HTA, I receive the following IE Script Error: Line 25, Char 1, Error: Object required: 'ObjFso', Code 0, URL: file://X:/Windows/System32/netmap.hta carrying on from there, I get several other script errors, but I think they're all related to the first message. 2. Logical Disk Information. This is more of a suggestion, I think it would be beneficial to have column titles on the disk information (e.g. Drive Letter, Label, Free Space, Total Space) 3. Default mount path it would be good if the default path to the mount point was set as the image location when the HTA is started. 4. Completed capture. it would be good that after the message telling you that the capture is a success that the next box that currently says "do you wish to reboot" - "ok" or "cancel" be changed to the OK button saying reboot, and the cancel button saying return to the hta to continue imaging or something. 5. Mount Image. This is currently not working, it just flashes past a dos box. I think the wimfltr.inf actually needs to be installed, this could be done as the hta is being loaded, so people don't need to manually inject the drivers. hope this helps, I haven't had a chance to test it further. keep up the excellent work.
  5. You should receive some sort of Microsoft Nobel Prize for all your hard work, I just came back from TechEd 2007 NZ a week ago, and I was telling one of the MS guys about this project and he was really buzzing. I know there is the other imagex gui out there, but after looking into it, while it exposes all the imagex functionality, It doesn't stream it all into the ease of use that this solution provides.
  6. Thanks for the USB advice, The basic issue, is that at the moment when running a capture, unless you sit there and watch the progress to make sure no error messages pop up/imagex crashing. Once the imagex command is complete (regardless of success) the HTA pops up a message saying the image is complete, and to press okay to reboot (or something like that, I can't remember the exact wording) the problem being sometimes the image wasn't successfull and there is no indication anything went wrong. what I would like if possible, is for the HTA to remember the specified wim path/filename and check to make sure the image is actually there after the imagex capture command has been processed, so instead of saying the current "complete, press okay to reboot....(or whatever it says exactly at the moment)" it should say: image PATH\FILENAME.wim successfully captured and verified (just a simple check to see if this file is actually where it should be and exists), press "OK" to reboot or "CONTINUE" to return to Imagex HTA. this last little bit of simple fault checking would be a huge help for me, normally I make a habbit of quiting the HTA or openning a command prompt and checking for the file manually after a capture, but the one time I forgot as I was in a hurry, the capture had failed and I didn't notice until I had formatted the drive, installed Windows and then went to recover some data. (bugger)
  7. ah, I missed the wimscript.ini post.. must be blind. I edited my last post with my other request whiile you were posting the above reply, hopefully you didn't miss my almost begging request for some basic fault checking when capturing. regards
  8. good to hear news on this great project, The new features sound awesome especially the new partitioning system, if you do need an early adopter to test, I have several test machines I can play with. the only other features that would be nice having are the following 1. Fault Detection e.g. Recently I started a capture of a working system as a backup before a rebuild, the chkdsk completed successfully and the imagex started processing directories/files and I went off to lunch, happy and content, when I got back it was up to the "click OK to reboot....). which I did and then rebuilt the PC, what I forgot to do, which I normally make a point of, is checking to make sure the WIM is actually there. Unfortunately it wasn't. now I know this HTA just runs the imagex command so if an error message popups when unattended it is missed. is there a way for you to modify the hta to check that the wim file (that was specified when the capture is started, is actually at the specified location. (e.g. performing a dir/s filename.wim or something). this feature would be invaluable. 2. excludes system, e.g. picking a text file to set the files/folder to be excluded. or failing that, an easier way to set custom excludes. On a side note, Does anyone know if it is faster to boot windows pe from a usb key (USB 2.0) or a CD-ROM?
  9. Hi, this project looks awesome, I had been using the Imagex HTA but have found several limitations and the project itself unfortunately seems to have ground to a halt on the MSFN board. I have read through all the posts and was wondering if someone could tell me the current status of the gui itself. Does it currently work in Vista PE, what features currently don't work, and is there a completion time frame?
  10. the simple partitioning options has my vote. I would like the options.... 1. Leave disk as is (no changes at all) just just imagex 2. Wipe the drive, create one large partition and format (quick) 3. Wipe the drive, create one large partition and format (regular) 4. Custom (opens diskpart.txt with an example of 2 partitions) also I was wondering if you could add an option to choose the drive letter to apply the image to when clicking install. keep up the excellent work geezery.
  11. the disk id i'm talking about is the id of the physical disk, e.g. run diskpart list disk, it gives you the id of each disk, the first disk is always 0, second disk is always 1. if you have a partition on a single hard drive, the first and second partition will still be id 0, as it is on the same physical disk
  12. while you're adding the disk info, I'm not sure if it is even possible but could you also display the disk id, this would be very handy for identifying multiple physical disks, compared to partitions on the same disk.
  13. just tested the new version geezery, it works great, except there is two \\ in the capture new image prompt. also any chance of displaying the current labels of the disk and the available/free disk space in the logical disk information?
  14. this would be most appreciated. @ Pretender69 that first background is great, could you please post it.
  15. Looks like another excellent revision Geezery, hope you don't mind but I think I will manually add the iframe version of the disk info system I showed you, your version only seems to show the c drive. and doesn't really help with knowing where my usb drive with my wims are. In regards to imagex info, and my diskpart list volume writing to the ram drive. there are no issues with it, as long as there is enough free memory, but that is something that always needs to watched with winpe. Looking forward to see what you are planning for the next versions capture update.
×
×
  • Create New...