Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

travis_san

Member
  • Joined

  • Last visited

  • Country

    Canada
  1. Thanks ilko_t, this works now. To clarify, the nlited source installed via RAM load works fine. However, nlited source + IE7 slipstreamed creates errors in text mode. I was considering cdob's post on how nlite breaks the naming convention in txtsetup.sif and yet this is functional if the source is an ISO created by nlite. I noticed these ISOs are Joliet, whereas XP_RAM.ISO was not. I simply added set mkisofs_option=-R -J to mkISO_RAMload_sort.cmd to enable Joliet. This works; no missing file errors in text mode. Thank you for your help guys. I will test this on real hardware soon.
  2. Thanks ilko_t and cdob for helping me out. Oops, this is not a problem. I had been resetting the vm between text and gui setup. There is a 'WIN51IP.SP3' file in the root if that is what you mean. Yes, I did RAM load this way by linking the usb drive as a virtual drive. Between the text and gui setup I could not change the boot order of physical drives without resetting the vm, so I tried adding this to menu.lst: title find and load NTLDR of Windows NT/2K/XP find --set-root --ignore-floppies /ntldr chainloader /ntldr This does not work ("File not found" in VirtualBox, instantaneous reset in Qemu). However, this entry does work if booted from a mounted ISO (I'm puzzled as to why) instead of a linked usb drive. This was the method I used to create a successful install. Is this how you tested it in a vm or did you use a different method? I tried this as you said and the install works perfectly. What can I do to slipstream IE7 without generating missing file errors in text setup? Can you help me understand why these errors exist with the RAM loaded version and not when mounted as a CD? I've attached txtsetup.sif from my IE7 slipstreamed source. Here is my menu.lst (it's just the same as in cdob's first post): title Loading XP RAM install - /Inst/XP_RAM.ISO ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) #(fd1) optional, required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_RAM.ISO (0xFF) map (hd0) (hd1) map (hd1) (hd0) map --hook chainloader (0xFF)/I386/SETUPLDR.BIN TXTSETUP.7z
  3. I'm getting errors in the text setup that say these files can't be found: advpack.dll.mui icardie.dll.mui iedkcs32.dll.mui ieframe.dll.mui iepeers.dll.mui iernonce.dll.mui iesetup.dll.mui ieui.dll.mui ieunatt.exe.mui inetcpl.cpl.mui inseng.dll.mui msfeedsbs.dll mshta.exe mshtml.dll.mui mshtmled.dll mshtmler.dll.mui urlmon.dll.mui winfxdocobj.exe.mui wininet.dll.mui If I skip each of these files, the setup continues ok until the GUI setup where I receive the error "The file 'asms' is needed" and I cannot proceed further. The source I used to create XP_RAM.iso was an nlited XPSP3 with IE7 slipstreamed and an $OEM$ folder just containing a cmdlines, a batch script and reg files. I have no issues with this source when mounting it as a CD. Testing done in Virtual Box and the ISO was loaded via a usb flash drive. I feel like I'm missing something obvious...

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.