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.
In Windows Vista and Windows 7 .NET framework (all versions) runs fine, however, in XP certain network drivers and programs on system startup can cause the .NET Framework Client 4 Profile or .NET Framework 4.xxxx NGEN service to become unstable during the log on session. Some times you will notice a 30 second to 2 minute delay in windows XP startup of Network Connections and some startup applications (usually seen in notification area). The cause of this is most likely that service. If you find that this fix doesnt change the start up time problem, then it is recommended to keep using this service, as most up-to-date programs perform better with the new .NET Framework Updates. FIX: 1) Hold Windows Key +R, and release. 2) In Run command window, type: services.msc 3) search for .NET Framework 4.xxxxx NGEN 4) right click to change properties of that service. 5) Set the service to "Manual", apply settings and reboot 6) If it still is slow, set the service to "disable". 7)If you know it's not the service, set it back to "Automatic" Most likely you could have a startup program causing the issue Although this is now off-topic, you can still experiment with windows startup services and startup apps. through MS Configuration Tool: 1) access the Run command window (just like above) 2) Type: MSCONFIG 3) Click on Services or Startup, change and apply settings you assume could be the culprit. 4) If you want to revert everything back to normal, simply access the MSCONFIG tool again (SafeMode is faster) 5) On the first window (1st tab), just click on "Normal" startup, apply and reboot. Hope this was helpful
I know this thread is a little old, but it has some useful info. and I can share my useful info. if anyone is interested. I would like to know something: There are already ways to partition a usb drive with multiple partitions with various tools, and it's possible to show the drives in windows with a tool/glitch I know w/o any filters,etc. BUT MY QUESTION IS: will making the 1st partition of the usb to be DOS-bootable allow the usb to be fixed in all versions of windows? Or simply, will it be shown as a fixed drive if the usb is loaded onto a new computer w/o the microdrive filters? BTW, if u want to know how I manage to partition my usb drives, I used MiniTool Partition Wizard to resize and set all partitions as Primary and one Active, then I safely remove the usb drive and run the showdrive.exe command found in %systemroot%\system32\showdrives.exe, which shows all the drives. It works for me, however, it wont work on certain XP Live CD's. I find that in Safe Mode it works flawlessly, so it could be a windows service sometimes. For the "showdrives" trick, in certain scenarios it will only work if you unplug the drive 1st before executing showdrive.exe, any further ejects can cause the USB not to show until you reboot your system. Heres a tool i like messing with, BOOTICE.EXE (Latest 0.9 build). My favorite MBR is Wee63.mbr, you can easily customize which loaders and where the loaders are located on the drive, so if you have a multiboot USB with one partition, you can use different loaders in different directories, and just customize your menu.lst or .ini file to direct each bootable img or installation DIR. It's even better with multiple paritions, because all you have to do is just direct the loaders in wee63.mbr w/o any further file editing. Also, you can direct boot manager loaders, like plpbt.bin, which allows you to chose which media device and partition to load from during boot (i highly discourage plpbt.bin because it has some rediculous bugs when loading a usb with multiple partitions, that contain a loader that is the same as the 1st partition on the drive).