Member Avatar for The Dude
  • 3 Contributors
  • 5 Replies
  • 117 Views
  • 23 Hours Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

’s post kicked off the thread and the replies from and show the two predictable reactions: excitement and speculation about what comes next. Treat early vendor announcements as signals, not instant action points. They tell you what the vendor plans to work on, but they do not change support or compatibility for machines already in production.

Practical steps for anyone managing machines or thinking about upgrading:

  • Build a short compatibility matrix for critical apps and drivers, and keep it updated.
  • Create a test lab (VM snapshots are fast and reversible) that mirrors a few representative hardware/software combinations.
  • Run a staged rollout: pilot group → larger test group → full deployment, and log results at each stage.
  • Verify driver/firmware updates with vendors and keep rollback images or scripts ready.
  • Use an update-management tool appropriate for the environment (centralized patch services, configuration management, or staged Windows update tools) to control timing.

A note for the “switch to a different kernel” crowd: large shifts in core architecture are expensive and break drivers and legacy software. Vendors typically balance innovation with backward compatibility to avoid disrupting customers. Expect major redesigns to have long lead times and heavy emphasis on migration tools, compatibility layers, and developer guidance.

For long-term planning and to follow official notes and known issues, consult vendor release and lifecycle resources and plan updates into regular maintenance windows so testing and rollback are built into the process (Windows release health, Microsoft lifecycle policy, WSUS documentation).

Recommended Answers

All 5 Replies

Member Avatar for jbennet

sp1?

theyve already announced that there starting develiopment on vistas sucessors (vienna/blackcomb and fiji)

Member Avatar for Dortz

fiji is just microsofts codename for sp1.

vienna (it has been officially renamed) will be the next windows, after vista.
now, think of vista as the future, right? is vienna generally supposed to be the future's future? no, I don't think so. vienna is going to be something entirely different. so different in fact, that microsoft has already started design research on it. with vista, they toyed with and upgraded explorer, pulled a few key things you do every day, slapped them on the side, and re-invented the look and feel. with vienna (reportedly, this isn't for sure) the whole package gets tossed out the window, cat and all. A complete reinvention of how the user interacts with the computer. but that's not until something like 2012.

After reading up on the 'press release,' which i found out is an e-mail, not an official statement, I found also that fiji will go live along with the release of longhorn. (the server edition of vista) I'm not suprised that sp1 is already in the works. microsoft learned a 'lot' with the release of sp1 and sp2 for xp, and sp1 for vista is looking like it will be the most well prepared. By getting thier testing data from large companies (individual users can't be part of TAP. boo.) they can get the essential data from running vista under a large network with heavy demands. information they couldn't get in the beta testing phase. It's not so much as 'planning for the worst' as it is 'planning for the inevitable.' They know they will need it, and they are just planning ahead.

Member Avatar for jbennet

i think ms should base vienna on unix

Member Avatar for Dortz

I'm sorry for my skepticism, but i'm pretty sure ms is going for revolutionary, not impeding. I'm sorry, but i think unix, and i don't think 'user friendly.'

Member Avatar for jbennet

well Mac OSX is based on UNIX and its the most easiest system there is

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.