Recommended Posts

Dude! We released longhorn just for your own enjoyment..not to fight like poop..

And yes, this release is to show a bit progress of how lh is doing. Of course it is not perfect, but it does get better in newer builds which is obvious not accessible to the public yet. Like always, patience is needed, and things will get better.

-ThunderRiver

Might I suggest you guys release a better version to show the direction MS is taking with Longhorn. The build that was out is pretty much crap. Looks like a half hearted attempt to add crap to XP. and even call it XP professional in the setup and boot, until u try to setup Media Center. Please release something a little better. Longhorn is suppose to be completely different??? Not in the one released.

Installers and a lot of parts of the code still show the old version tags until late beta. What's so special to that? Also it's a goddamn pre-alpha! Is that so hard to understand? PRE ALPHA, TECHNICAL SYNONYME FOR EXPERIMENTAL BUILD!

:hmmm:

Installers and a lot of parts of the code still show the old version tags until late beta. What's so special to that? Also it's a goddamn pre-alpha! Is that so hard to understand? PRE ALPHA, TECHNICAL SYNONYME FOR EXPERIMENTAL BUILD!

:hmmm:

Nevermind, you missed the point anyway.....

Dude! We released longhorn just for your own enjoyment..not to fight like poop..

And yes, this release is to show a bit progress of how lh is doing. Of course it is not perfect, but it does get better in newer builds which is obvious not accessible to the public yet. Like always, patience is needed, and things will get better.

-ThunderRiver

Might I suggest you guys release a better version to show the direction MS is taking with Longhorn. The build that was out is pretty much crap. Looks like a half hearted attempt to add crap to XP. and even call it XP professional in the setup and boot, until u try to setup Media Center. Please release something a little better. Longhorn is suppose to be completely different??? Not in the one released.

Really?Wow thanks for letting me know, I guess its not obvious enough that Longhorn hasn't been in development long enough yet to be completely different from XP. Why don't you people understand this! Whistler was so much like 2000 in every way at the beginning to and now look, its XP.

Installers and a lot of parts of the code still show the old version tags until late beta. What's so special to that? Also it's a goddamn pre-alpha! Is that so hard to understand? PRE ALPHA, TECHNICAL SYNONYME FOR EXPERIMENTAL BUILD!

:hmmm:

Nevermind, you missed the point anyway.....

No I didn't. You were whining how crappy the alpha was, I told you WHY :hmmm:

Meh, who cares? Anyway for all those with Longhorn as their OS for the moment, tell me one MAJOR difference between Xp and it (as of now, knowing something big will happen in the future). I've seen a couple of screenshots of Longhorn on the net and it looks pretty slick.

if anybody still cares, here are some new screenies of longhorn build 4183. they are said to be fake, but u make the call...

http://www.xbetas.com/modules.php?name=Nuk...rticle&sid=1072

***Fixed Link***

Edited by LilBlueDawg

Pahleeze... Do you know how builds get counted? 1 build each day during development! How to you get from 3683 to 41xx in such short time? And oh, the build difference between XP and .NET/Longhorn is because they increased the server build from 2505 to 3505 the time the appropriate build was out, to "seperate" the two.

lol you know if MS just changed their build incrementor, or just kicked off a new build starting at say 5105.xxxx whatever, that would really throw some of you wouldnt it?

I would love to work for MS, id go into work on my day off and mess with the build no#, release some screenshots and look at you all argue it muhahaha.

That'd be the life :p

lol you know if MS just changed their build incrementor, or just kicked off a new build starting at say 5105.xxxx whatever, that would really throw some of you wouldnt it?

I would love to work for MS, id go into work on my day off and mess with the build no#, release some screenshots and look at you all argue it muhahaha.

That'd be the life :p

Heh.. and then you would get the sack for violating the Microsoft NDA's, and screwing up their number versioning system :)

:D

On the same note... I've been invited to the Core group, I've now access to all MS beta programs, incl the Longhorn alphas. Now I know where these early leaks come from.

If your not lying, then congratulations :p

I was lying... lol!

I have no clue how to get in there. I guess it requires good history on Betaplace/Windowsbeta and vouching from one of their core group members. NFI.

I heard from a reliable source that you needed to be a well known Microsoft employee and have one of your top bosses (with access to the special area on the intranet with Longhorn) vouch for you, then you get access, sounds about right, this 4xxx build is probably fake, there was a guy who posted his "4xxx" desktop in December Desktops about 3-4 days ago :unsure:

Dunno, from what I heard the core group is just a bunch of overzealous beta testers. And if you act like one, and someone of a MS products beta team vouches your you, you get in. But also I heard all seats are filled, so you can pretty forget about it.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Turbo Pascal was my first real programming experience more than 30 years ago at university. I mostly taught myself from the included examples and help documentation, because the university only taught the basic syntax and philosophy of Pascal, without going deeply into Turbo Pascal’s advanced features. I still remember when I discovered that I could embed assembly language directly into Pascal code, call BIOS functions, manipulate screen memory, use mouse interrupts, and control peripherals from my programs. That opened huge doors for me. Programming back then felt really fun, direct, and close to the machine. What I loved about Pascal was its readability and the almost instant compile time. Turbo Pascal was an amazing environment, but unfortunately Turbo Pascal for Windows 3 did not feel like it fully carried that legacy forward. Later, Delphi got things back on the right track after the messy transition to TP for Windows. Sadly, Delphi suffered from years of uncertainty as it moved from Borland to CodeGear and then to Embarcadero. That instability made many developers lose confidence in it, even though Delphi itself remained a powerful and productive tool. I still work with Delphi from time to time, but I definitely miss the old days of Turbo Pascal.
    • I hope this encodes in to AV1 or AV2 as currently tiktok uses h265 and h264.
    • Qualcomm reportedly in talks to build custom video chips for TikTok parent ByteDance by Karthik Mudaliar Qualcomm is reportedly in advanced discussions to provide custom chip-design services to Chinese tech giant ByteDance, the same company behind TikTok. According to a report from Reuters, Qualcomm could be involved in designing custom silicon tailored for ByteDance's massive data-center workloads. If it goes through, the deal would make ByteDance one of Qualcomm's early anchor customers for its fastly growing custom chip-design division, For years, Qualcomm was the king of making smartphone processors and modems. The company has also been moving into the PC ecosystem and other formats such as on-device AI for Android XR headsets. However, this particular deal is about Qualcomm's custom Application-Specific Integrated Circuits (ASICs). For a platform like TikTok, ByteDance needs hardware that can help it ingest, process, and serve billions of short-form videos daily. Generalised hardware is no longer the most cost-effective and efficient route, which is why ByteDance is trying to develop custom Video Processing Units (VPUs). VPUs designed specifically for ByteDance’s algorithmic needs could drastically reduce data-center power consumption and improve encoding speeds at an unprecedented scale. The underlying tech behind these processors is actually from Qualcomm's recent acquisition of AlphaWave Semi, a high-speed connectivity specialist company. By combining AlphaWave’s high-bandwidth IP with Qualcomm’s architectural expertise, the company could begin mass production by the end of 2026, if the talks go through. All this also comes at a time when U.S.-China tech relations have dwindled. Escalating trade frictions between Washington and Beijing have severely impacted the export of high-end AI chips from U.S. firms like Nvidia, AMD, and Lam Research. Yet, the Qualcomm-ByteDance discussions show that U.S. tech companies are still actively seeking growth avenues and are open to doing business with China, where regulators still permit. Reuters notes that the outcome of this deal could be uncertain, and ByteDance might also seek partners other than Qualcomm. via Reuters | Image via DepositPhotos.com
  • Recent Achievements

    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      456
    2. 2
      +Edouard
      164
    3. 3
      PsYcHoKiLLa
      117
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      69
  • Tell a friend

    Love Neowin? Tell a friend!