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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

2 Neutral

About shorterxp

Profile Information

  • OS
    XP Pro x64
  • Country

Recent Profile Visitors

2,005 profile views
  1. APologies for my absence FilediskA is exactly what I need. i.e.The ability to load / autorun any .iso in one double-click proceduce (for machines without iso tools previously installed). The relevant iso is the only way to install the software (its distributed this way). Those who download the iso may not know how to mount it and so would apprecite the simplicity of a single exe next to the iso itself, which can be distributed alongside the iso. Upon trying FilediskUA, the issue arises that upon clicking the iso to mount it (after FilediskUA has been installed) the iso doesn't autoplay / autorun the installer splash screen. I seek a way to run autorun automatically and this likely would require a separate vbs/cmd script, in turn necessitating a self extracting archive. However as I have already expressed in previous post, SFX can either unload files into current dir. or into a temp dir. More ideal is by way of latter, where files [filediskUa installer, script] are unloaded to temp directory, where the script of which not only installs filediskUA and subsequently mounts the relevant iso (thats beside the SFX) but also runs the autoplay of that iso - and that all of these steps occur upon clicking the SFX.exe. The quesiton is, how may a script in the now temp folder 'retrieve' the directory [nominally a string] from which the SFX that spit it out ab inito, is located? What i've done so far: In a folder theres a custom installer, itself a SFX, which installs IMDISK without reboot. Separately theres a cmd script, which when clicked mounts the iso + launches the autorun - this script resides adjacent to the iso. In this state, there are 3 files, 2 if not counting the iso. To merge those 2 would be ideal. Open to all suggestions. I should mention this should work on all windows XP to present. Edit: filediskuA does not appear to work and is temperamental when mounting.
  2. I long for a time people stop saving as docx and save as .doc. there are zero gains from the docx format over doc (regarding MS word) I do use the compatibility pack on XP to open docx. All this itteration bullcrap will one day be looked back upon by future generations and viewed as pretty dumb and unecessary. The only reason for software updates is mortages and hungry mouths. period. FYI I just use the main download from MS website. never had a problem using MSo 2003 thus far
  3. To avoid even bigger choclate coated banana, here is the situation / requirement Ideally, a single executable (thats beside relevant .iso) of which does the following when clicked: - mounts iso to virtual drive - launches the autorun.exe on the newy created virtual drive. This is so to aid users who may be unfamiliar with how to use archive software / have necessary space to unpack the 8gb iso and/or may not know how to mount virtual drive. A exectuable downloaded alongside the iso makes for a more intuitive experience. The autorun inside the iso guides the player with the remainder of the installation. The content is only ever officially distributed as an .iso, which is why I though this would be a good idea. My current, working, though not ideal solution involves Imdisk_custom.exe (as seen 2nd previous post) in the same directory as the iso, as well as a batch script beside that. Although Imdisk installs perfectly, it would need to be manually uninstalled - this is ok. There is however the small annoyance of two seperate files, now next to the .iso. A single .exe would be better. I propose a SFX self extracting archive with slimmed down verison of the original 7z archive contents, that 1) installs imdisk, 2) mounts the iso 3) runs autorun in one single instance - However the SFX extracts the batch script to temp folder, which of course is no longer in the same directory as the .iso, so I ask if there is a way to pass the launch directory on to the script. In other words, If example.iso and example_sfx.exe (latter of which does steps 1,2,3), are in C:/example_folder, and example_sfx.exe is launched, is there a way for the script now in a sfx temp folder / orphaned from the iso, to query (and use) initial launch directory, in this example "C:/example_folder"? For example: [...] %windir%\system32\ImDisk -a -m Z: -f %Mystery_Launch_Dir_variable%\prbf2_1.5.0.0_full.iso Z: START "" autorun.exe Perhaps source_path or start_path is a better descriptor. An interesting aspect of SFX, which may be related is the sfxcmd variable. Perhaps this can be used in target script? Regarding filedisk: Both these are true. Modifying the IMDisk install.inf as you suggest in order to avert installation is daunting to me, so I might try filedisk too if its suitable. I note Filedisk v15 readme states reboot is required and files to be placed in sys32 so maybe it isn't suitable? Thanks for the help
  4. Is it possible to run imDisk standalone? i.e. run the VirtualDisk Service temporariliy without incurring installer, nor the need to run service at startup?
  5. For some reason 'Mount with IMDisk Virtual Disk' appears on all files in explorer, even irrelevant ones like cmd. Expunge the following registry key to prevent this. HKEY_CLASSES_ROOT\*\shell\ImDiskMountFile Here is my silent repack with this fix included: OneDrive (761kb). It's a SFX archive. and yes Chocloate banana is a habit I must admit. Thank you for your invaluable assistance once again//
  6. Ok, I uninstalled SPTD rebooted the OS and installed IMGDisk alone and it seems to work without SPTD. This is so much easier, I cannot believe people recommend to use SPTD + Daemon when IMGDisk does it off the bat without messing around with drivers at Unattended. In hindsight so much time was wasted making a silent Daemon installer (i.e. post #1) -.-
  7. Update: I managed to track down the patch, here is the code that supposedly fixes the bug. Not tried it yet. ' [ MS .NET Framework 4 - WinXP Slow Boot Fix v3.1 ] ' This Script will fix silently in the background a Microsoft .NET Framework 4 bug that causes a slow Windows XP boot up. ' This Microsoft .NET Framework 4 bug can occur, for example when reinstall Microsoft .NET Framework 4 or when installing new Microsoft .NET Framework 4 Updates. Set objShell = CreateObject("WScript.Shell") Set objFSO = CreateObject("Scripting.FileSystemObject") ExeFile = objShell.ExpandEnvironmentStrings("%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\ngen.exe") If (objFSO.FileExists(ExeFile)) Then objShell.Run Chr(34) & ExeFile & Chr(34) & "eqi", 0, false End If WScript.Quit It's a .vbs script.
  8. Does anyone have a mirror of those Hotfixes please?. I'd like to slipstream them in a recent nlite install. In any case, I'm curious if when these are present on systems running on non-target motherboards, if they will cause problems or not.
  9. Hi, Is there an easy way to "track" services behaviour at log on for windows XP? I installed a ethernet device driver, upon reboot + logon (and everyone subsequent logon) explorer loads however majority of windows stuff refuses to open (some non .net apps can). Things like Device manager, network connections, control panel, won't open for circa 2minutes. I suspect that a service which is supposed to run at startup impdes the usual logon sequence. Is there a tool out there that can monitor the sequence? FYI: It's definately the ethernet driver that does it because upon fresh install of XP (which takes but a minute) everything works as expected until IT alone is installed. Even after uninstall, the hang persists. Trried both manual installation of the driver via device manager and the provided installshield package, both lead to the same end. Cheers fellas EDIT: problem goes away if I Disable the connection in Network Connections (or device in device manager). Very strange
  10. Is anyone familiar with this bug and if so, how do you approach it? For anyone interested: the bug occurs when one installs .NET framework 4.0 on clean XP SP3. Apps at log on are delayed for 2minutes on the first reboot after installing 4.0 and occurs everyboot thereafter until 4.0 is otherwise uninstalled). In a pre-made image of XP, available on the web, there is described a feature called "F4SBF Patch v2.0" which supposedly fixes this. I don't want to link to the page due to forum policy. I'm curious what this update entails. References https://rejzor.wordpress.com/slow-windows-xp-startup-fix/ https://social.msdn.microsoft.com/Forums/vstudio/en-US/cb75c4dc-e0af-4b22-85b2-c2c1b08bfea1/why-does-net-framework-4-client-profile-slow-down-boot-time-network-creation
  11. Can you suggest a lightweight alternative to daemon tools ?
  • Create New...