Jump to content
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. ×

Maelstorm

Member
  • Content Count

    269
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

1 Neutral

About Maelstorm

  • Rank
    AT Field Pattern Blue

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    Windows 10 x64
  1. I know quite a few people have been looking for this. So here it is. The location in the registry for the content, layout, position, and size of items on the Windows 10 Start Menu is here: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudStore I am going to warn you though, much of the data is binary. It looks something like a C struct or attributes of a C++ class. There does appear to be UTF-16 encoded strings in the data too, so it looks like it copies the shortcut information into the database. I wouldn't try to modify the data as it may corrupt your user prof
  2. I went from Windows XP to Windows 10 a few years ago and I have gotten used to it. Right now, I'm trying to add a php file template to show up on the New context menu when I click on the desktop. I found a few way on the web, but I can't seem to get it to work. I've been modifying the registry directly. Here's what it currently looks like. Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.php] [HKEY_CLASSES_ROOT\.php\OpenWithProgids] "VSCode.php"="" [HKEY_CLASSES_ROOT\.php\ShellNew] "NullFile"="1" "FileName"="%ProgramData%\\Microsoft\\Windows\\Templates\\template.php"
  3. I've been looking through the files of a WinPE 3.0 and for the life of me, I cannot seem to find where WinPE starts setup which installs Windows. Now I know about cmdlines.txt, winpeshl.ini, and the registry key HKLM\System\Setup that runs winpeshl.exe. So, from boot.wim, how does windows setup get started?
  4. I can build Windows XP All In One install DVDs in my sleep. Well, my script builds it. I have been looking through the forums, online, and the deployment documentation from Microsoft, but I am still confused about how this works. Here's what I have been able to gather so far: Instead of an i386 directory, there's a install.wim file that contains the installation image. Instead of winnt.sif, the unattended answer file is now an xml file. There is the Windows System Image Manager which shows a bunch of components and packages which I have no clue about. Windows PE? In WIn XP, Win PE was m
  5. Is there a command line disk wipe utility that works on WinPE? I'm running WinPE 1.6. I tried HDDERASE.exe and it won't even load.
  6. I have an update. It turns out that dd does not work under WinPE 1.5/1.6. So, I tried one of the other tools mentioned, specifically mkbt. It seems the following command line works quite well: mkbt -x -v -c Z: C:\BOOTREC.DAT So I've integrated it into my boot disk. This is all strictly testing right now. I am currently writing a HTA menu system that will run under WinPE to control everything based on what the user selects. As for testing, the following is the batch files that I am using to do this with under VMWare 5.5: MakeDisk.cmd @ECHO OFF START /WAIT CMD.EXE /C "\Program Files\Misc\
  7. My brain went for a walk on that post. Heh, this entire thread actually. I think dd would be the best tool to use in this case since that is the tool that I am most familiar with. I'll play around with it and see if I can get an automated setup working. Thank you so very much for the help.
  8. Ok, I think we have a misunderstanding of what I am asking for. I did get this to work, manually, but I need a automatic method to do this. I'm not asking for the Master Boot Record, but the *VOLUME* Boot Record. The MBR that we all know and love is at CHS 0, 0, 1. This everybody knows about, and all the tools and suggestions given deal with that, except mkbt which gives an error about it only works with floppies. What I'm asking for is the boot sector *INSIDE* the partition that is pointed to by the MBR. That's what BOOTSECT.DAT is when you install the Recovery Console. The volume boot
  9. Those tools are nice, but not what I am looking for. I need a tool that will read the MBR, then write the specified volume boot record to a file. Just like WINNT32.exe does when you install the Recovery Console. It makes a file called BOOTSECT.DAT in the cmdcons directory of the boot partition. I'm looking at writing my own, but I would rather not as I know absolutely nothing about C/C++ programming under Windows. -EDIT- I did find a tool called Findpart http://www.partitionsupport.com/utilities.htm that does what I want, but it's a 2 step process to make this work. The problem is getting
  10. Ah, so that's what the problem is. Can you recommend a command-line sector extractor so I can extract the boot sector of the partition? I don't have any tools to do that for hard disks. I've searched all over google, and I did find a couple of tools that would seem to work, but they do not. Something like mkbt.exe from BartPE would be just the ticket that I am looking for.
  11. How do you boot Windows PE 1.x (I'm using 1.6) from a second primary partition or harddisk using boot.ini? I've tried several things, but have yet to get it working correctly. Note that this isn't a dual-boot of WinPE in the same partition as WinXP, but it's in a different partition/drive. Here's the layout: Harddrive 0: Part 1: ~475GB Primary/Active - Windows XP Part 2: ~20GB Primary - Windows PE Here's what I have tried: In boot.ini, copy the WinXP line and modify it to point to D:\i386 :--: Failed Installed cmdcons, copied bootsect.dat to D: and point to that in boot.ini :--
  12. Any word from Redmond about a OEM Preinstallation Kit for Windows 7? Or is it even needed anymore?
  13. Actually, Microsoft learned their lesson with the Vista driver fiasco. Windows 7 will use the same exact drivers that Windows XP uses...From what I am told.
  14. Unpack deploy.cab on your Windows CD. It's in \Support\Tools. Once you have the file unpacked, look at ref.chm. It has most if not all options as well as other information and tools.
  15. Add/Change the following lines to your unattended setup: [unattended] UnattendMode=FullUnattended UnattendSwitch=Yes TargetPath="\Windows" Repartition=Yes WaitForReboot=No OemSkipEula=Yes OemPreinstall=Yes
×
×
  • Create New...