Jump to content

raskren

Member
  • Posts

    377
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by raskren

  1. Looks like you nuked the ISO. Contact Microsoft.
  2. Obviously, nobody knows. I'd like to add that you are NOT using Longhorn Vista Beta 2. Beta 2 has not been released yet. You are most likely using a Post Beta 1 build that has been tagged as Beta 2.
  3. Here's another insightful and helpful post, Crash&Burn. Just last night I upgraded the RAM in my Xp laptop from 512 MB to 2 GB. I just slid it in, powered on, and Windows Xp worked like a charm. Look ma', no editing vcache values!
  4. Sigh. Yet another wonderful example of how forward thinking Windows 9x is. You can add more than 512 mb of RAM. It requires some modifications but it can be done.
  5. I've removed a few USB perhipherals but nothing else. Regular Windows Xp installs just fine and I've had MCE installed on this box before.
  6. The post Beta1 builds do not have drivers for the ICH5R chipset or Silicon Image SI3114 controller. That's about all I know. The setup routine is different though. You can now load these drivers using a floppy, cd rom, or usb disk.
  7. I thought this reg key only turned off the low disk space popup balloon. Best solution is to create a CMD script to run the command-line defragger with the force (-f) switch. defrag.exe %systemdrive% -f -v pause Copy and paste into notepad and save it as "force defrag.cmd" or something similar.
  8. First, I posted this here because it is a Windows Xp issue and not at all related to Media Center...even though it is Media Center. Got it? I just added all the Post SP2 hotfixes and MCE Rollup 2 to my DVD (SVCPACK method). At this point it is not unattended. I have also added two RAID drivers that I need for my machine. Installation appears to run normally. After the second restart I see the Windows Xp image with the blue loading animation for just a second and then the machine reboots. I am not able to boot into safe mode at all and turning on boot logging does not generate a log. To complicate matters even further, this installation works in VMware! I haven't had MCE on my machine in ages so I am unsure as to whether or not this is an issue with my hardware or my install source. I looked at some of the logs, namely setuperr.log and there are no entries. Any idea what could be wrong? I may try installing this onto another machine in a day or two.
  9. This is pure FUD. 1. - Vista will not require a new monitor. Vista will run just fine on the 800x600@60Hz POS you're using now. Playing HD content from an HD or BluRay disc might require an HDMI compatable monitor but this is Hollywood's requirement, not Vistas. Ergo, this requirement will be in all operating systems, not just Vista. 2. - OpenGL is far from broken. Full screen OpenGL apps will run at full speed. Windowed OpenGL apps get emulated via DirectX when DWM is turned on and the performance hit for doing this is tiny. If you must have your windowed OpenGL app running at full speed you can just turn DWM off (Shift + F9) 3. - What uses too much memory? As in Xp, there are bits and pieces you can turn off/disable. 128 MB seemed like a lot when Xp was released. Also, Vista is more than a year off so I would not base your opinion of the OS on the beta bits alone. 4. - The best argument yet. Oh let's see: Completely hardware accelarated GUI, completely rewritten networking stack based on IPv6, completely rewritten audio stack, per-app volume control, easier image maintenance and deployment, easier installation, stricter driver quality controls, integrated Tablet PC and Media Center functionality, PNG icons with high-quality DirectX scaling and anti-aliasing, DPI scaling of the entire desktop and all applications, XAML icons, animations, and effects, network location awareness 2.0... Need I continue?
  10. Thanks for bumping this really old and quite useless thread.
  11. Turn off UAP from the Start Menu.
  12. There is no set-in-stone release date as of yet. They're shooting for the second half of 2006.
  13. The problem with a benchmark is it is going to be predominately hardware based. Read: it will stress the hardware, not the software. Any variance amongst the scores would all fall well within the margin of error for the test leaving us with inconclusive results. To further remove hardware from the list of variables the test would have to be run on bleeding-edge hardware: Dual-core CPU, 4GB RAM, SCSI hard drives in a RAID0 configuration, and possibly frozen and overclocked. We could probably remove the hard drive as a variable entirely by loading the operating system onto an iRam device. But with this hardware how do we test DOS? Windows 3.x? 95, 98, Me? We can't and that doesn't make for a good test or conclusive results. The "fluff" in Xp that many purists hate consumes memory and little else. Throw enough ram at Xp and it will run AS FAST as Windows 2000. When you add small kernel improvements like prefetching you might find Xp faster than 2000 when including application launch and system bootup into the results, contrary to popular belief. 2000 doesn't require as much ram as Xp. In a low memory environment an Xp box might be continuously paging to disk while the 2000 machine processes along happily. This is a scenario where an older OS is faster but probably doesn't answer the original poster's question.
  14. You would need to have the shortcut modify boot.ini directly. I suppose this could be done with VBscripts but that's beyond the scope of my knowledge. This is of course, assuming that there are no third party applications available. I don't know of any off hand.
  15. Don't restart it yet! Force your computer to use an IP address (static address) that you know is within the usual DHCP range and see if you can get to the router's admin pages and flash again.
  16. Xp Pro for me. Reason being, Xp runs the latest hardware. Dual-core, hyper-threading, etc. If you mean the OS with the least overhead (I don't see DOS 6.22 or Win 95) well then that would be the oldest OS. Not exactly a meaningful evaluation.
  17. That stop error occurs when the system can "see" but cannot access the boot disk. Most often caused by a missing or corrupt driver. By loading your ISO as a virtual drive you probably gave Vista access to a driver that was in the ISO. After the first restart the driver is no longer available and Windows crashes.
  18. If you do not have a video card that can do DX9 effects in hardware you will not see glass effects. If your DX9 video card does not have an out of the box LDDM driver you will not see glass effects. NV6xxx and 7xxx cards do not come with an out of the box LDDM driver even though they can render DX9 effects. You can download the Nvidia LDDM driver directly from Nvidia. If you do not have a DX9 card and/or LDDM drivers you will not see glass, even with TweakVista. The option to enable glass on unsupported cards was for build 5048 in which they tried to constrain to a 9800 Pro or Nv 5600 or something.
  19. If you can't find the GUI tools (they are there), you can always do it from the command line: attrib %systemdrive%\*.* attrib -r boot.ini edit boot.ini <now make changes, save, quit> attrib +r boot.ini BTW, to modify folder properties (show hidden files/folders, file extensions, etc) open any explorer window, click the button that modifies the navigation and preview pane, a drop down list will appear, click on "Show Classic Menus." This restores, File, Edit, View, Tools, etc.
  20. [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Longhorn" /NOEXECUTE=OPTIN /FASTDETECT /USENEWLOADER multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /NOEXECUTE=OPTIN /FASTDETECT See where it says "default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS" That number after "partition" in parens should match the boot.ini entry for your default OS. In the example above, Windows Xp is the default. In order to modify boot.ini you must set it's attributes to read/write e.g. not read-only to Windows.
  21. OMG! Try using Google? http://www.google.com/search?hl=en&q=Longh...G=Google+Search LUA is least privilege user account. It is the new permissions model that will appear in Longhorn. It is present in Beta 1 but turned off by default.
  22. Thanks But althoug I try to install to an IDE drive the setup files is copied to the SATA drive as my Win XP is on that and I wan't a dual Boot and don't wan't to reinstall both op's on IDE drives. Guess I have to go and buy myself some DVD discs so I can boot directly to the instal DVD but think it should work with mounting the ISO also it have worked with previous Longhorn builds but guess they have changed something now? <{POST_SNAPBACK}> If I had an nickel for every time I've seen that stop error... There is a known issue in which you mount the ISO image and run setup.exe from within Windows. Stupid IMHO. But that's another topic. The only way to fix is to boot from a DVD disc.
  23. Change the sound output device to/from Direct Sound to WAV output. See if that helps. This has worked for some and failed for others.
  24. Rumor has it they'll be XAML based which can be a vector markup language among other things. We should also see some very nice true 3d animations, shading, reflection and blurring - all vector based. This is just rumor and is subject to change. Everything in Beta 1 is raster at this point.
×
×
  • Create New...