Jump to content

ppgrainbow

Member
  • Posts

    713
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by ppgrainbow

  1. This problem occurs on Windows 2000 as I'm running it in VMware Player right now. I'm also wondering if this problem also occurs on Windows XP x64 and even Windows Embedded POSReady 2009. I'm wondering if tampering the expiration date of the XML files in the MUAUTH.CAB and AUTH.CAB files will fix this or not. It seems that Microsoft was unaware of this mess.
  2. I have entered my website into the Exception List with the correct link. I've attempted to draw something at my oekaki board, however it partially works. When I attempted to save using PaintBBS, I get this error message: Also, when I try to save a test drawing using ChibiPaint, for some obvious reason, the applet stops working and several minutes later, this error message is displayed: Normal and animated OekakiBBS, ShiPainter and ShiPainter Pro applets work correctly. When visitors use the Java run applet for the first time, they're greeted with this information: When I click Yes, Java works. I'm gonna be updating the site more sometime this weekend to reflect the changes in Java 8 Update 20+.
  3. Hey there! I currently operate my oekaki board for over a decade now. When I updated to Java 8 Update 20 (and higher) on my Windows Vista Ultimate x64 PC, any attempts to access the Java applet on my oekaki throws this error message: Oracle had been informing people for sometime that Java would hard block unsigned applets. I had failed to realise that the oekaki that I've been running has unsigned applets and Oracle has been calling it a policy issue. Is there any way to fix the issue involving Java and unsigned applets without having to break legacy compatibility with older browsers? (I'm currently running Windows 95 under VMware Player with 64 MB of memory, Firefox 1.5 and Java 1.4.0.4 installed and I don't have a problem with it at all. If you feel that I placed this thread in the wrong part of the forum, I apologise.)
  4. I don't understand. You haven't been able to test a 2 Gb or 8 Gb because you have not any handy. OR You have been able to test a 2 gb and a 8 Gb BUT they did not work 100% correctly. OR You decided to NOT test a 2 Gb and a 8 Gb (though you would have been able to test them) because you believe they won't work correctly jaclaz I don't understand too. I think it would be best to contact StarTech regarding this issue.
  5. Okay, I think that I finally solved the problem. It's the capacity of larger CompactFlash cards itself and not the SATA-to-CF drive. As far as I know, although the BIOS will recognise larger CF cards in POST, the Windows operating system will NOT boot correctly, if not at all. I have tested the boot process with the First Champion 1 GB 80x CompactFlash card and well do you know, Windows Vista booted up without problems. I haven't been able to test a 2 GB or a 8 GB capacity CF cards as they may not work 100% correctly with the SATA to CF drive. The SATA-to-CF drive treated the Kingston Ultimate 32 GB 266x drive as a floppy drive and since it had trouble booting properly, I ended up ruining the card and tossing it in the trash. Edit: I tested it with some of the CF cards and found that the First Champion 1 GB CF card worked, but as far as I know, that CF card is not bootable. I also tested it with a Kingston 1 GB CF card and the CF card has issues being recognised when Windows Vista boots up. I wish that I had the time to test which CF cards work with the Startech SATA to CF drive, but I don't right now.
  6. Wait a minute.If the thingy is SATA connected, it should be "hot swappable", or not? http://mt-naka.com/hotswap/index_enu.htm jaclaz According to the NewEgg review on StarTech's SATA-to-CF card: For some reason, the CF card when inserted into the SATA-to-CF drive would not load correctly when Windows Vista resets the devices after it boots up as one NewEgg reviewer complains that the the drive is either incompatible or poorly made. I should try the HotSwap! utility to see how things go from here.
  7. The only way that I can try different CompactFlash card sizes is turning off the computer, ejecting the current CF card and inserting another one. I tried a 2 GB capacity CF card the other day and Windows Vista still stalled after boot. I was hoping for a solution so that I don't have to eject the CF card for at least one minute when Windows Vista restarts all of the devices after it boots up. Update: I re-enabled the hibernation feature. This is the case when the power went out about a hour ago. Anyways, for some reason. The BIOS would detect the CF card inside the SATA-to-CF drive, but when Windows Vista boots up and resets the devices, the CF card inserted into the drive would not load properly. I'm wondering if there is a way to fix this buggy issue here via a registry hack or a utility?
  8. I knew it. Do you have any idea what can be done that can make Vista detect the CF card in the drive at boot without having to hang on startup?
  9. Like I said before, the boot delay occurs in the classpnp.sys and it only happens when the CF card is inserted inside the SATA-to-CF adapter.
  10. Yep. It's the adapter itself and not the CF card. This boot delay issue occurs only if the CF card is inserted inside the SATA-to-CF adapter.
  11. I'm gonna be uploading it onto my OneDrive account and privately send you a note. I've noticed that while Windows Vista was attempting to boot, I've noticed a long wait in the CLASSPNP.SYS and partmgr.sys driver delays of 620.01 seconds! Ouch! I always though that crcdisk.sys was the issue as it was determined in Safe Mode, but it appears that I was wrong. The datestamps on the classpnp.sys file is 2009-04-11 and for the partmgr.sys, it's 2009-04-11 for one file and 2012-03-20 for the other two files.
  12. Okay, I would like to post a update to this forum post. I used this command to perform the boot trace below: Although, that it performed a boot cycle trace, it traced the output on the root directory of drive C. Therefore, when the tracing was finished, I decided to move it to the C:\Output\Boot sub-directory. But when I tried to perform this command: I ended up getting this error message: Nevertheless, I viewed the following files in the C:\Output directory: 1. First, looking at the boot_BASE+CSWITCH_1.etl and boot_BASE+CSWITCH_1_km_premerge.etl files. Between around 10 to 315 seconds elapsed time (ET), no activity was being sampled. Between 315 to 520 seconds ET, activity usage started to spike with almost 2,500 hard faults at 320 seconds. The shutdown_BASE+CSWITCH_1_km_premerge.etl file stated that it took 44 seconds to reboot the computer. Not bad. 2. And then it comes the C:\Output\Trace\boot_BASE+CSWITCH+DRIVERS+POWER_1.etl file. The analysis stated that it took about 80 seconds longer than boot_BASE+CSWITCH_1.etl/boot_BASE+CSWITCH_1_km_premerge.etl files If you look in the Driver Delays section of this file, you'll notice that partmgr.sys took 310.78 seconds to load and CLASSPNP.SYS taking 1 ms shorter to load. Numerous delays between the 320 to 600 second ET mark indicate long delays with fltmgr.sys delaying for as much as 8 seconds in the 420 to 470 second ET mark. Something sounds fishy here and the cause of this issue is difficult to decipher here. If you have the Windows 7.1 SDKs installed should I upload the files from the C:\Output\Trace directory onto my OneDrive account so that the issue can be looked into? If so, please let me know.
  13. Thanks for the help. I'll look into reinstalling the Windows 7.1 SDK. However, this requires me to uninstall the Visual Studio 2010 runtime first. Installing the Windows 7.1 SDK will reinstall the VS2010 runtine.
  14. Sorry for not responding earlier, but this behaviour occours only when the CompactFlash card is inserted and it doesn't matter if the card is partitioned/formatted or not. In a forum post by asicnewbie in early May 2008 complianed that the Addonics SATA to CompactFlash adapter doesn't work with the majority of the cards that the user owns and stated that the user's PC will either sit there for a very long time (and will eventually error out) when the user tries to acces the drive or that it simply hangs the Windows XP operating system: http://arstechnica.com/civis/viewtopic.php?f=11&t=127190 On a side note, I'm wondering if it's possible to obtain xbootmg/xperf without going through the hassle of reinstalling the Windows SDK or not? :\ At one point, I went into Safe Mode and found that the hanging error points to the crcdisk.sys which has a timestamp of 2008-01-19. So, I'm wondering if a outdated crcdisk.sys has to do with this booting issue or not. I might try a smaller capacity CF card to see if it makes a difference or not soon.
  15. Hey there! I had someone install the StarTech 3.5" SATA to CompactFlash SSD adapter in the 3.5" drive bay and so far, the computer is working good. Windows Vista can detect what CompactFlash card is inside the 3.5" SATA to CF drive bay without any major problems. However, I'm running into issues after I insert the CF card in the 3.5" SATA to CF drive bay and turn the computer on: 1. The BIOS will recognise the CF card that is connected to the 3.5" SATA to CF drive bay as it is connected on SATA Port 4 on the ASUS M5A97 R2.0 motherboard. However, when Windows Vista attempts to boot up with the "© Microsoft Corporation" Segoe UI text and the green progress bar above it, the green light indicator on the SATA to CF drive goes off and the red hard drive LED stays on and the computer hangs indefinitely. In a interval of one minute, the hard drive LED will go off and the green light indicator on the SATA to CF drive goes on for a short period of time. One temporary work around is that when I try to eject the CF card from the SATA to CF drive, the hard drive LED light would go off. I would leave it ejected for up to one minute and it would let the internal hard drive on SATA Port 1 continue to boot the Windows Vista operating system. 2. When there is data being read or written on the CF card, not only the green light indicator is blinking, but the hard drive LED light is blinking as well and it's not supposed to do that. I have a couple of questions to ask to try to remedy this if possible: 1. Is there a way to fix the issue that will allow Windows Vista to boot successfully even if the CF card is inserted inside the internal SATA to CF drive? 2. In any event there is read and write activity on the CF card, is there a way to stop it from using the hard drive LED light? The model number on the StarTech SATA to CompactFlash card is 35BAYCF2SAT. The model number can easily be searched on Google. The issues that I mentioned above are minor and do not affect the functionality and performance of my computer. On a sidenote, in order to successfully recognise the CF card inside the the SATA to CF drive, I had to set the SATA ports to use AHCI mode and not IDE mode.
  16. I went from Windows XP (retail upgrade) to Windows Vista (OEM) and then Windows Vista to Windows 2000 when my laptop died and then back to Windows Vista (retail). The reason is that I admit that I used the old computer for more than 11 to 13 years, I found that it is just simply too slow and no longer useful to remain on Windows 2000 (which has been unsupported for more than four years). By using Windows Vista on this new computer for a couple of years, I will be able to still use software that is still designed to run on the aging OS. Windows Vista will remain supported until April 2017, btw. I'm very happy with the OS that I'm using right now.
  17. As far as I know, I'd avoid the 256 GB capacity flash drives that are worth just $25 and do not work reliably. I'm getting a lot of negative reviews regarding the flash drive that you mentioned. One person called it a scam...a actual "8 GB flash drive with properties hacked"...aka counterfeit 256 GB flash drives that only show up as 8 GB. Seriously, I think that Amazon needs to ban the seller for selling defective products. The fixed price for a new 256 GB flash drive right now is at least $150. A product with the highest review score on Google would go for at least $180.
  18. That's what I've been thinking all along. I forgot to set the _NT_SYMBOL_PATH when I used !symfix to try to fix the symbols. :\
  19. check your PM and look if my compile works for you I got your note and found that the 64-bit version of Stella 4.0 worked on Windows XP x64 and Windows Vista x64 worked when it is compiled with Visual Studio 2012 and without AVX support! I will take this issue to the AtariAge forums, if possible.
  20. I think that I will head to the AtariAge forums and let them know what could be up with the 64-bit version of Stella 4.0. In other words, I think that I will have to stick with the 32-bit version of the software built with MSVC 2013 as this will most likely be the latest 32-bit version of the compiler that will work with Windows XP/Vista.
  21. I see what you mean there. I'll take a look at the link that you showed me and discover the advantages of running 64-bit software over the 32-bit version.
  22. It's hard to tell. AVX code support has been present since Visual Studio 2010 SP1. Although the AMD FX-4300 has AVX support, AVX code is only present in Windows 7 SP1 and later. Developers are starting to use AVX code for 64-bit apps built with MSVC 2013. This is not a issue in 32-bit apps built with MSVC 2013. If you think that my comment is confusing and doesn't make sense, let me know.
  23. The current official version of Stella is compiled with MSVC2013 and can be compiled using MSVC2012. The source can be found here: http://sourceforge.net/projects/stella/files/stella/4.0/stella-4.0-src.tar.gz/download
×
×
  • Create New...