Jump to content

ppgrainbow

Member
  • Posts

    713
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by ppgrainbow

  1. Thank you for the heads up. I tried putting in the DLLs required and for some reason, the Windows 95 version of Paint still failed to save or open images under Windows NT 3.51. The same thing applied to the updated files from PAINT95.EXE.
  2. Windows NT 3.51 Workstation and Server is based on the Windows 3.1 codebase. Certain amounts of software (such as Office 97 and Corel Draw 6) that works under Windows 95, should work under Windows NT 3.51. The reason why I wanted to use Windows NT 3.51 is that it takes up a lot less disk space and memory than Windows NT 4.0. The only downside is that Windows NT 3.51 is missing certain features that only exist under Windows NT 4.0 and Windows 95 respectively. The end goal is to try to get remaining features from Windows 95/NT 4.0 Paint working under Windows NT 3.51. Here's a brief run down: 1. With Microsoft Paint from Windows 95 / NT 4.0, when you post a screenshot that has the original size of 1024 x 768 and the image attributes in Paint has a fixed image size of 500 x 500, you can have the full image resized. This feature doesn't exist in Windows NT 3.51 and parts of the image is displayed when it is pasted in Paintbrush. 2. You can use the magnifying glass to zoom the image between 100% to as high as 800% for example. Under Windows NT 3.51, you can only use the Zoom In and Zoom Out feature (found in the View menu). 3. The Win95/NT4 Paint included PBRUSH.EXE as a stub. Therefore, it doesn't work at all under NT 3.51. Also, in NT 3.51, there were two features that were available. They were the Cursor Position feature in the View menu and the Omit Picture Format feature in the Options menu. Some of the features were changed in Windows 95/NT 4.0 respectively. Here is what both versions of Microsoft Paint look like: The app on the left is the Windows NT 3.51 version of Paintbrush, the app on the right is the Windows NT 4.0 version of Paint. I'm wondering if there is a way to import some of the code from Windows NT 3.51 Paintbrush to Windows NT 4.0 Paint to make the features such as saving and opening PaintBrush files work under Windows NT 3.51. I couldn't read the post because MSFN was down most of the day.
  3. I'm currently running Windows NT 3.51 Workstation with SP5 installed under VMWare Player. I managed to replace the Windows NT 3.51 Paintbrush with Microsoft Paint from Windows NT 4.0 Workstation SP6. The good news so far is this: Most of the Microsoft Paint functions work as-is under Windows NT 3.51 as it did with the original version of Paintbrush. The bad news are the following: 1. In the File section, the Open, Save and Save As... features do not work. To work around this issue, you would have to either exit Microsoft Paint or select "New" to save the image where you will be prompted for a file name and where can you save the image. I have not tested the Save as Wallpaper (Tiled)/(Centered) feature. 2. In the Edit section, the "Copy to..." and "Paste from..." features don't work. You would have to copy the image to another Windows NT 3.51 compatible image editing programme and paste it there. 3. When you select a TrueType or Bitmap font, there is no option to select a font face name and the font size do not show in the Fonts window. 4. In the Options section, the "Get Colors..." and "Save Colors..." features do not work. How can I get Microsoft Paint from Windows 95 or Windows NT 4.0 fully working under Windows NT 3.51? 1. Would there be a patch or code modification to fix the bugs that I listed above? 2. What files would I need to replace if necessary? Sorry if I'm failing to provide enough information, but I'm gonna be turning in for the night soon. Would it be good if I can try to provide screenshots to see what I mean by this?
  4. Thanks for telling me. I kinda have the feeling that it will be nearly impossible to fix the hard links in the Registry Editor without having to re-install software from scratch to the second hard drive, wouldn't it?
  5. Thank you so much for telling me. Unlike Windows XP/Server 2003 and below, why does the structure of Windows Vista use hard links that affects moving installed software to a second hard drive?
  6. It was wired to the onboard Ethernet cable with the DSL going to the phone/DSL jack.
  7. The model looks the same. There is already one in this house. Here's what it looks like: http://sishardware.com/imgs/a/a/f/e/p/netgear_dsl_modemrouter_combo_wireless_4___port_frontier_b90___755044___15_rev_3a_1_lgw.jpg It is a brand made for Frontier Communications. There was another brand made for AT&T. The hardware would work if a 100' ethernet cable from the family room is connected to the onboard Realtek Ethernet cable. I disabled the onboard Ethernet network in the BIOS. If I were to use the onboard Ethernet network instead of the wireless-G PCI router, I would have to enable it in the BIOS.
  8. I did use Test-WUN to extract the contents of the 16-bit installer for COA2 using WUN and it worked. For example, I used the command line to copy the SMBX directory over to drive D. I did the following: 1. I opened up the COA2 utility and change from the old address of C:\SMBX to D:\SMBX. 2. I clicked on "Change now". 3. When the COA2 utility tries to change the address to the folder by searching for any shortcuts, INI files and registry entries. So far out of 1,233 shortcuts, 2 entries were changed. 2,468 INI files were searched and none of them were changed. When I viewed the change records, it showed a long name found, but when the procedure was completed, the files were moved successfully. I'll get back to you if there are any problems with COA2 under 64-bit Windows Vista. I'm gonna be doing a XXCopy to copy some files from the first hard drive over to the second hard drive.
  9. Thank you! The bad news is that: 1. Parts of the hard drive caddy for the Tecra 720CDT laptop broke. 2. The fan inside the motherboard on the laptop stopped working. 3. The part that I ordered off of Amazon is deemed unwanted and it has to be sent back. In short, after more than five years of use, I'm gonna have to give up the old laptop and toss it to the recycling centre. From now on, I will most likely run Windows NT 4.0 under VirtualBox, VMware Player or Virtual PC instead.
  10. This is one of the reasons why I have been offline for almost two weeks. I just couldn't get the Netgear 7550 router to work at all. I even had a technician from Frontier Communications inform me that in order to get internet access working with second wired router, I would have to sign up and pay for their service when I already signed up. The only way to resolve this is to get a 100' ethernet cable that will connect from my computer to the router in the house and connect it to Ethernet port 2.
  11. Hello! Sorry that I've been offline for nearly two weeks. I recently had a technician install a second Western Digital Black 1 TB hard drive on my computer and I want to move some of the software installed on drive C to drive D without re-installation. I got the second hard drive for Christmas and had the technician install it the day after. I also used a utility called XXCopy to copy the files to a different drive and most importantly preserve the date and time the folders were created. Under Windows NT 4.0, Windows 2000 and Windows XP, I used XXCopy to copy the files, preserve the timestamp of the folder and COA2 (Change of Address) to change the link to the software and the registry. This is not the case, because COA2 will not install on Windows Vista and higher. So, tell me this. Which freeware utility compatible with Windows Vista will let me move installed software from drive C to drive D without re-installation and preserves the date and time the folders were created? Thank you for your time.
  12. Thanks for the help. I had to run frontier.exe as administrator. However, I have a new problem here. When I try to get setup to detect the internet connection on the Frontier Netgear 7550 router, I get this error: But when I tried the Gigaset SE567 router, it got as far as attempting to detect the DSL line and wound up with this error message: As far as I know, I'm stuck here and can neither get the routers mentioned to work.
  13. I'm having a problem installing the router on my Windows Vista Ultimate x64-based PC! I had my sister and my father connect the Frontier Netgear B90-755014-15 router to my computer and installed the software associated with the router. However, when the setup attempted to check the gateway and network connections, the Frontier Installer crashed with the following error message: Viewing the problem details produces the following: The Belkin USB wireless router connected has the Frontier1638 SSID. However, the internet connection has been terribly crappy for the last couple of days. The wired router that I'm trying to install, has the Frontier8943 SSID. How can I fixed this?
  14. Alrighty. I'll go for the PLoP Boot Manager to see how it goes.
  15. I'm currently running Windows 95 SP1 under VMware Player 6.0.4 (host OS: Windows Vista) with the VMware SVGA II graphics card driver installed and I've run into a problem with a old graphics editing programme called Adobe Photoshop 3.0.4 (released in June 1995). The application works under Windows 95, however when I try to tinker around with the toolbox, edit the canvas or attempt to save a file after a few minutes, Adobe Photoshop 3.0.4 crashes: Clicking on Details prior to closing Adobe Photoshop 3.0.4 displays the following: I'm wondering if the problem relies on the Windows 95 operating system itself (including the updates that I installed), Adobe Photoshop itself or the KERNEL32.DLL module that hasn't even been updated yet. I searched for answers to resolve this issue, but it has been no help at all. Is there a way to fix this problem? 64 MB of system memory and 4 MB of video memory is allocated to the guest OS under VMware Player. Update: I found that Adobe Photoshop 3.0.4 isn't fully compatible with Windows 95. Updating to version 3.0.5 apparently solved the issue.
  16. Thank you for the help. I will bookmark the link for future reference. According to this comment by Quad in June 2005, the Toshiba Tecra 720CDT is a old unit that was manufactured in April 1996. Booting directly from CD-ROM is not possible. All OS installations on the Tecra 720CDT have to be done from the floppy drive. Later Toshiba Tecra models have the ability to boot from the floppy drive. I'll look into finding ways to boot from CD using the PLoP Boot Manager from the floppy drive.
  17. Thank you for the heads up. Windows NT 4.0 RTM installations are limited to the first 4 GB FAT or NTFS v1.2 partition on the boot hard disk. Windows NT 4.0 RTM takes up at least 110 MB of disk space and with the memory maxed out at 144 MB, it shouldn't be too much of a problem to have at least a 192 MB swapfile. The 7.84 GB limit only applies to the Windows NT 4.0 version of NTLDR and NTDETECT.COM files. By the way, how can last accessed times be disabled in the Windows NT registry? Edit: I forgot to mention that the Tecra 720CDT laptop lacks the capability to boot from CD-ROM. So, in order to setup Windows NT 4.0, I would have to operate from the boot diskette, create a FAT partition (up to 2 GB), format it, copy all of the files from the \I386 directory on the Windows NT 4.0 CD-ROM installation setup and type WINNT /B. Using the /B makes the installation floppyless, creates a \$WIN_NT$.~BT directory on the boot drive and copies the boot files there from the source directory on the CD-ROM.
  18. After more than a year of running Windows 95 OSR2 on the Toshiba Tecra 720CDT laptop, I'm have found that it is becoming unreliable. I already bought a Compact Flash to IDE hard drive adapter and I will use one of the SanDisk Ultra 8 GB Compact Flash card to use as a internal hard disk. I bought a Syba Best Connectivity 2.5" IDE 44-pin to Dual Compact Flash Adapter for $14.17 and I'm going to use the SanDisk 8GB Ultra CF card (SDCFH-008G-A11) as the boot device on the Toshiba Tecra 720CDT laptop and the SanDisk Ultra 8 GB (SDCFHS-008G-AFFP) card as the PCMCIA drive. This is especially the case since ATA-33 IDE hard drives are no longer sold as new. I'm considering re-installing Windows NT 4.0 Workstation on the Tecra 720CDT laptop after getting the CF card installed on the CF-to-IDE card although I should be aware that neither the Tecra 720CDT laptop nor Windows NT 4.0 supports hard disks and other media larger than 7.88 GB...so, I'm maxing out the hard drive and memory. Since Windows NT 4.0 uses the NTFS 4.0 file system, how well will Windows NT 4.0 play out when it is installed on the compact flash card? I personally found that compact flash cards are more reliable than MLC SSDs as far as I know. Thoughts, anyone?
  19. Just for the record, both the KB872952 article, as well as the actual hotfix remain available from MS to this day... Thank you for telling me! Unfortunately, it's been more than a year since I had Windows NT 4.0 installed on Virtual PC and unfortunately, I removed the VM. If I have the time, I will recreate the Windows NT 4.0 VM and re-install the OS.
  20. Here is the MS article that has a Direct UpdateCatalog Link in it (as given by dencorso). Again, the link I gave with "LinkID=" in it does *not* work. That one (apparently) directs to a script that check the OS. http://support.microsoft.com/kb/323166 To clarify: 1 - Windows Update is to get *only* Windows Updates for *your* OS 2 - Microsoft Update is to get *all* Microsoft Updates for *your* OS/MS-Software 3 - Microsoft Update Catalog (aka Windows Update Catalog) is to *search* for *any* OS/MS-Software x - Office Update is (now) obsolete, but *some* can still be found on the Office site for direct download. The whole problem appears when *before* the change #2 website that it *failed* because of "muweb.dll -> 7.6.7600.257". Regressing to v256 (apparently) "cures" it and as well allows "undoing" MU to use just WU again (if you desire). There *is* "some sort of" a problem with the XML's dates and the Redirects found inside the "WindowsUpdateAgent30-x86.exe" v256(built)/v257(my hybrid) build. You see, when using the *original* "v248" directly from MS, WU does *not* work, so we resorted to a "built" one. *However* auto-updates *upgraded* module(s) to "v257" which caused the problem. Do read the whole thread and all embedded links. HTH @ppgrainbow - DUDE!!! Did you *not* see that above??? You *are* aware that the files get "updated" from time-to-time, right? That's *exactly* why we got "bit" at an inopportune time. I already got it.
  21. The downgraded version of muweb.dll (Microsoft Update) will only work until 3 December 2017 at 11:59:25.79 AM PST. Any attempts to access Microsoft Update after this point will throw a 0x80072F05 error! At that time, Windows Embedded POSReady 2009 will still be supported, but how will users be able to access the site if the date is set past the expiration date. I had to set the date to 2017-12-03 to reflect this and then revert back to today's date. This was tested under Windows 2000, btw.
  22. I think that there is a problem with Microsoft Update itself! I can't believe that even POSReady 2009 users can't even update using Microsoft Update at all. Update: I solved the problem by using v7.6.7600.256 version of muweb.dll. I'll check the Windows XP VM sometime this weekend and go from there.
  23. That's odd. Only Windows 2000, Windows XP and Server 2003 have this problem. And as far as I know, tampering the expiration date to 2099 doesn't work, because Windows Update will redownload the CABs containing the original authorization.xml files. I'm wondering if there is a solution to this issue. Currently, Windows 2000 has 7.6.7600.256 of wuweb.dll, Windows XP has version 7.6.7600.257 of wuweb.dll. Neither versions of the wuweb.dll worked.
  24. Sure it's not related to unsupported OSes, but it's clearly related to the sudden deprecation of muweb.dll v. 7.6.7600.257, not at all to MUAUTH.CAB and AUTHCAB.CAB, despite the 2014-11 <ExpiryDate> inside one or both of them. And, then again, why in the world did muweb.dll v. 7.6.7600.257 get suddenly deprecated at all? I don't know why this would happen. A lot of customers who are still using Windows XP and Windows Server 2003 aren't too happy that they can no longer install updates due to the sudden deprecation of muweb.dll v. 7.6.7600.257.
  25. It sure occurs with Server 2003, as can be found posted elsewhere, over the 'net. Then again, after I downgraded those two files MU started working again in the two XP machines I hadn't yet given this month's updates, so I got them up-to-date. After rebooting I've checked and the muauth.cab with the <ExpiryDate>2014-11 remains there. I think that's not the right lead to pursue, right now. That's what I've been thinking. This issue is not related to unsupported OSes or the Windows Update website itself, but the expiration date of the files in MUAUTH.CAB and AUTH.CAB.
×
×
  • Create New...