Jump to content

djackson

Member
  • Posts

    39
  • Joined

  • Last visited

  • Donations

    $0.00 

About djackson

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    Windows 7 x64

djackson's Achievements

0

Reputation

  1. Thanks for that....now to test it out, however is there any documentation on how to use the Wizard Editor? Edit: found a Tutorial on myitforum . com
  2. I'm testing deployment of Windows 7 images in a workgroup environment via MDT 2010. I have edited bootstrap/customsettings.ini to auto-logon to the deployment share, etc., and about the only screens I get now are to prompt for the computer name. Image deployment works fine. However, is there an inbuilt way to get MDT to prompt to create a new user and password, or an external app I can script to do the same, as part of the LTI process?? I've tried the NewUser tool from the XP/2003 Unattended forum, but it is unsupported under Windows 7. Any advice appreciated
  3. Sorry to relaunch an old post... I'm just updating my WPI USB disk and keep getting a similar problem, but mine is only related to downloaded and updated apps. How do I clear the unsafe flag on the downloaded file? ---------8<--------- Please disregard...I found the setting...cheers!
  4. Hi, I know the BIOS section you mean, unfortunately the MOBO doesn't have that option. Also tried clearing the BIOS via the on board jumper, but no success there either. Thanks for the assistance, I've disabled sleep mode on this PC and will just do a normal shutdown and resume. Cheers! Dave
  5. Hi, That's the article I saw. Just tried power down, remove power cable, wait 30 seconds (no stand-by light) and restore power... unfortunately no success. My i-mate still requires a hard reset to be recognised again. This could be just one of those things I'll have to live with, like UAC. Cheers and Seasons Greetings! Dave
  6. Hi, I've (finally) taken the move away from XP and installed 7 Ultimate x86 (all updates installed). Whenever the PC now resumes from sleep mode my i-mate PDA2K (running Windows Mobile 6.1) that was previously recognised and sync'd looses the plot. It comes up as an "unrecognised device". I've done a quick search and the advice was to power down and reboot the PC, and all would be right with the world again. I'd already tried this without success. Removing and reconnecting the i-mate is also unsuccessful. The only fixes I've found that work are to disable sleep mode on the PC, or to do a hard reset of the i-mate and let it be re-recognised. While neither solution is ideal, both could be lived with more or less, just wondering if anybody else has come across this and either found a fix or a better solution... Cheers and Seasons Greetings! Dave
  7. Hi, Could the CreateSthortcut JSCRIPT be modified to allow placing of shortcuts within a folder on the desktop? I tend to copy software that needs manual installation to %SYSTEMDRIVE%\Software and create .lnk files to them and place the .lnk files in "%ALLUSERSPROFILE%\Desktop\Manual Install". The current JSCRIPT only places the shortcuts in "%ALLUSERSPROFILE%\Desktop" As a work around I'm moving the shortcuts. Best Holiday Season Wishes! Dave ...no need to worry about my prior request about a CHANGEDIR command, I've worked my way around this, and now know what I should have been doing!
  8. Hi, Would it be possible to add a {CHANGEDIR} command, to set the current working directory? Cheers!
  9. Hi, When ticking the check box for "Disable Category Check Boxes" (options/general screen), the placement of the Previous / Next navigation line (main screen) gets moved down and is no longer visible. Cheers
  10. Hi. I know Win2000 is now definitely over the hill, but could BootFolder be updated (or backdated) to include Win2000 support? Thanks
  11. the format should be; DIRCOPY "[source drive][source path]" "[target drive][target path]" eg DIRCOPY "%ALLUSERSPROFILE%\Start Menu\Programs\nLite" "%ALLUSERSPROFILE%\Start Menu\Programs\Development" this will move "nLite" folder into the "Development" folder hope this helps
  12. Glad to help. Just tried a full method 2 install in VMWare, and found it unpacks to HDD @ about 1500Mb. So maybe a little over the top. But then HDD are large and cheap. What I tend to do now is integrate into a dummy build, then take the created DriverPack files and do a manual integration using this method http://www.msfn.org/board/index.php?showtopic=51406 You can then leave the drivers on the DVD, or have them on HDD, and they are processed at T-39. Excluding Graphics pack 'C', drivers from DVD/HDD is about 540Mb, which is a lot more friendly. If you do use this way, juggling for a multiboot disk can be fun.
  13. I may be wrong on this, but here goes... I'm assuming you are using DriverPack base module, and selecting method 1. If so, this can be a normal occurance. There is a MS Windows limitation in WINNT.SIF of 2047(?) characters in the drivers search path character line length. One work around that you've tried is to reduce the number of drivers, and hence the character line length, or try method 2 which writes the path info to the registry, instead of WINNT.SIF. Hope this helps...
  14. This has probably been covered elsewhere, but there seems(?) to be an easier way to slipstream both hotfixs and servicepacks into the full Office 2003 suite administrative installs. 1. perform normal administrative install, ie setup.exe /a, into your prefered destination path, eg "x:\Office 2003" 2a. download and extract the full servicepacks required to your prefered destination path, eg "x:\Office 2003 SP" 2b. download and extract the all hotfixs required to your prefered destination path, eg "x:\Office 2003 HF" 3. in "x:\Office 2003 SP" you should have the servicepack/hotfix *.msp files + ohotfix.exe, ohotfix.ini, ohotfixr.dll 4. edit the following lines in ohotfix.ini (watch out for the difference between Office and Visio) IsNormalUpdate=0 (where 0 = admin install, 1 = normal workstation install) AdminUsesShortFilenames=1 (where 0 = Visio, 1 = Office [1 also works for FrontPage, Project, OneNote]) AdminPath=x:\Office 2003\PRO11.msi (x:\Office 2003\PRO11.msi = the destination msi file for the application you wish to update)5. run ohotfix.exe (SP or HF), this will now slipstream any/all(?) .msp files into your Office application. You'll get a completion dialog at the end. 6. Burn to CD/DVD, and test running the setup.exe as normal. You may be able to combine steps 2a and 2b and slipstream all msp files (both SP and HF) at the same time (untested), but I prefer to slipstream them separately. I've tested this with Office, OneNote, Project, Visio and FrontPage under Windows XP, and slipstreamed servicepack 2 for each application + post SP2 hotfixs without issue. Have not tried slipstreaming hotfixs on top of hotfixs, it may work. I reslipstream all hotfixs over an admin install + SP. However, the same reg file issues exist that were raised by OverFlow above. The Office update site is aware of the hotfixs, but Microsoft update is not. Go figure... My unelegant workaround is 1. in a virtual PC install one application, ie, Office 2. go to Microsoft update, scan for updates, then install the updates 3. find and export the registry changes for that app for future use (you'll find them in a block, look for a hotfix number, eg, 924424) I had probs with using the same registry entries for different apps, thats why I this is so tedious. To test 4. reset your virtual PC to an Office free snapshot 5. install the same app from step 1 above 6. import the reg file from step 3 above 7. go to Office update, you're up to date (hopefully) 8. go to Microsoft update, you're up to date (hopefully) I'm no expert on ohotfix.ini, I was just following the splipstream instructions in this post and saw the .ini file and thought "whats this for?" and started tinkering. Seemed to work for me. As usual "caveat emptor" applies, ie, no care and no responsibility taken for damage caused to your PC setup during the creation of this process, always try it in a virtual PC first. Hope this helps...
  15. OK, have done some quick reverse engineering... Until the updated themes start to appear, try these changes worked for me... yeah, I know, a little knowledge is dangerous copy DefaultImage*.jpg from the \\WPI\Themes\Classic folder to \\WPI\Themes\"your theme" copy GenUID*.jpg from the \\WPI\Themes\Classic folder to \\WPI\Themes\"your theme" add the following code to the \\WPI\Themes\"your theme"\wpi.css file .ftxt { font-family: arial; font-weight: bold; color: #FF0000; font-size: 8pt; margin-left: 5px; margin-right: 10px; }


×
×
  • Create New...