Last time I checked this was not a Microsoft bashing site but everyone is entitled to their opinion. MACs are great, PCs are better. My guess is that since MS makes it so easy to develop against this would be the reason why Dexcom went the way it did. Also, the other noteworthy factor involved is the Dexcom software was created for the physician not the end user. The fact that your endo does not obtain the software to chart your data is more disturbing to me. The fact that you stumbled across the software and want to use it is great but Dexcom didn't create it for the end user rather the physician. And most physicians are likely to have the Professional version of Office at their disposal.
Wow, Out of 5 (yes 5) different windows devices and management software I use. Again, all for windows just like co-pilot. The Dexcom software s the ONLY software out of 5 USB devices, with issues just to get it working.
None at all are unable to print, None require MS software to print. None, except for Dexcom,
No other Windows software has no issues with USB or the endless list compatibility issues.
I have 38 years as a diabetic. There were square needles, one kind of insulin and no Pumps or CGMs and pee strips were the control mechanism.
As a 30 year software designer and developer, I just hate when someone does that job I perform daily since 1980 and does it so so poorly
Like most current Mac users, you compare your Mac to the much older Windows. And, quite frankly if I had to choose between OSx and Windows XP or before, I'd choose Mac. Since Windows versions 6.x have been around though, I'd never choose Mac now. OSx is very old fashion in too many modern computing methods these days. Plus, a major security risk. As far as your comment on over-priced look at Apple's crazy profits if you don't believe which company's offerings are way over priced.
First, you don't need Office. Open Office will open the files, and it's free. Also, there are ways to get the Dexcom software to work in the latest versions of Windows. There's a thread here on how to do that.
I'm a 30 year computer professional, supporting PC, Mac and Linux based systems. Macs are different, but by no means better. I can always find a fix for issues on Windows. Macs far too often have problems that nobody can fix. And Apple often refuses to help on these issues. Heck, get a virus on a Mac and Apple will ignore you (yes, they do get viruses) but Dell will fix a virus on a Mac. Go figure.
Sorry but this is a Dexcom issue, not a Microsoft issue. Another TuDiabtes user supplied a patch to allow the Dexcom software to work with Windows 8 I believe the Dexcom software has never worked natively on the Mac
Maybe the next Dexcom software release that works in the Cloud world will work on the Mac.
But who lnows??
Wow, The recommended version (and only supported version is Windows 7.I have no clue where you got XP from but I have not used XP for over 5 years or more. I have used as a primary systems, win 3, win 3.1, win 3.11, win XP, Win 7, Windows server 2000 2003 2005 2007 & 2010. ect. I developed in MS for years. I never touched a Mac before 2 years ago and I have not seen the BSOD since. This was a multiple daily occurrence on Windows.
Not I will not get into a ■■■■■■■ match with a Microsoft Salesman.
Just because you love windows and have a solution, please share. Please tell me the secret to printing or viewing the DEXCOM doc files on Windows 7 (as outdated as it is). "Windows file viewer" does not work.
What good is blood glucose levels if you cannot see what pump bolus was taken or carbs used for insulin/food ratio? You Cannot without doing a ton of manual work.
I'm running Dexcom Studio under Windows XP from Boot Camp on my Mac Pro (4,1). No problems here. Which if you think about it, is kind of amazing.
I doubt Studio will ever run under OSX. I have no doubt whatsoever that a mobile version of it will run under iOS before very long, and that will become the primary version and use case.
If this is the same bug as: "This computer is not configured to accept the 'Open' command for '.doc' files."
then that error is very annoying as well!
I used to have that problem on my Windows 7 machine, so Dexcom Tech support told me "the temporary fix" for it:
You have to go to the /Temp directory and the files show up in there if you click the Print button. For example, mine are in:
C:\Dexcom\Dexcom Studio\Temp
Since iOS devices do not support USB communications, how could it work? iOS is made to be a consumption OS, not a data/programming/calculation OS. Not that it couldn't be, it's just that Apple did not have that in their idea of what it should do and did not make such hardware to support it in that way. Just read an article on the iPad, in that Apple still doesn't have any idea how they want to market the device, in that they don't know how they want to present it with all it's shortcomings and all. The real fix IMHO is for Dexcom to make their sensor comm devices blue tooth and write an app. Though blue tooth is a battery hog compared to the comm they use in their device right now, so that's not a great idea either. In the mean time, there are a lot of good Windows 8 tablets that work with the Dexcom Studio very nicely. Along with a slew of things that the iPad still doesn't work well with.
The *.doc files are in that directory but the names are not anything like the report. For example: {E7140932-4E9C-4231-AA9D-08D93DEA93BC}_temp.doc . If you have set up several reports, this makes it time consuming to find the right one. I have Word Starter 2010 and Word Viewer 2003 on my PC.
As soon as I print a report, I rename it and move it to a better location, but that extra step is annoying.
This really should be addressed, especially since Dexcom knows about it. The Dexcom Tech support told me that "they are aware of this bug" back in January, and the weirdest thing is that it didn't initially happen when I started using Fabian's awesome Windows 8 fix (see link below) but after a while I started getting the familiar error.
I spoke with a Dexcom tech support person recently. They are developing an update to deal with the "not configured to accept the 'Open' command" and the Windows 8 issues. They are waiting for FDA approval.