Problems with SUNRISE IDE INTERFACE (Hardware MSX Forum)MSX Resource Center MSXdev 2008 - MSX1 development bonanza!              
              
English Nederlands Español Português Russian         
 News
   Frontpage
  News archive
  News topics

 Resources
   MSX Forum
  Articles
  Reviews
  Fair reports
  Photo shoots
  Fairs and meetings
  Polls
  Links
  Search

 Software
   Downloads
  Webshop

 MRC
   Who we are
  Join our team
  Donate
  Policies
  Contact us
  Link to Us
  Statistics

 Search
 
  

  

 Login
 

Username

Password




Don't you have an account yet? Become an MSX-friend and register an account now!.


 Statistics
 

There are 54 guests and 1 MSX friend online

You are an anonymous user.
 

MSX Forum


MSX Forum

Hardware - Problems with SUNRISE IDE INTERFACE

Author

Problems with SUNRISE IDE INTERFACE

MisterT
msx novice
Posts: 29
Posted: September 15 2006, 21:29   
Hi people,

Maybe someone of you MSX wizards can help me out here...

I Updated my Sunrise Ide interface to v2.4xx and i use a CF 512 card as HDD.
Now i go to partition it
It creates 16 parts of 32 MB, so far so good.
I boot up and use a Floppy disk to copy my programs to Harddrive.
also, no worries...

Then i boot up from Harddrive, everything works, except when i want
to execute a program from harddrive, (e.g. com files)

Then it gives me the message

Wrong Msx-dos Version !!!

While the program still works on FDD i cant run it from HDD it wont do nothing...

Please help if u had similar problems ....

mars2000you
msx master
Posts: 1723
Posted: September 15 2006, 21:41   
Try with typing first the following MSX-DOS command line :

SET EXPERT=ON
MisterT
msx novice
Posts: 29
Posted: September 15 2006, 21:47   
Thanks thats the problem.........

(i'm out of the Msx language for a while)

But explain it to me what does it do and why doesnt it work without ?

Thanks again tho and ill hear ur reply....

mars2000you
msx master
Posts: 1723
Posted: September 15 2006, 21:52   
This command says to the MSX-DOS system that you are an expert who knows what he does. It allows to skip the problem of the system waiting for a determined MSX-DOS version and 'seeing' that you use another version.
AuroraMSX

msx master
Posts: 1248
Posted: September 15 2006, 21:52   
manuel, I think this question deserves a place in the Ultimate MSX FAQ!
MisterT
msx novice
Posts: 29
Posted: September 15 2006, 21:56   
Ok i understand that part, but why would it say
wrong version while i use the same everywhere.....

I use COMMAND version 2.31 from the ROM drive of my Turbo-r
Its copied to my RAMDISK / It's on my HDD

So its the same version on all drives, so what causes
that problem ?
mars2000you
msx master
Posts: 1723
Posted: September 15 2006, 21:56   
Indeed, this question comes again and again ... I think I should also add something in the blueMSX manual !!!
mars2000you
msx master
Posts: 1723
Posted: September 15 2006, 21:58   
MisterT : you have version 2.41 on your HDD if I good remember ... So, there's conflict between 2 versions.
MisterT
msx novice
Posts: 29
Posted: September 15 2006, 22:01   
No i use the version out of the Romdrive of my TR-GT
on all drives (got me mixed up with somebody else)

But hey its working, but i am curious why it gives me that
bulls**t without any reason, it worked fine on my old harddrive
and now i use a CF card and a updated IDE bios and it gives
me problems...


Sonic_aka_T

msx guru
Posts: 2268
Posted: September 15 2006, 22:03   
Quote:

Ok i understand that part, but why would it say
wrong version while i use the same everywhere.....

I use COMMAND version 2.31 from the ROM drive of my Turbo-r
Its copied to my RAMDISK / It's on my HDD

So its the same version on all drives, so what causes
that problem ?

Wrong DOS version means DOS2 didn't detect the disk you're using as a proper DOS2 formatted disk. DOS2 checks the bootsector to see if it encounters a valid volume ID. If it doesn't find one, it assumes the disk is not a DOS2 disk meaning stuff like undelete and cache won't work properly. Since this could cause problems, DOS2 expects you to confirm you know what you're doing by setting 'expert' mode on. Supposedly you can fix this with the FIXDISK program that comes with DOS2, but I've never tried this, and I don't know if that'd work properly with a harddisk. Just put a SET EXPERT ON in your autoexec.bat, that'll also 'solve the problem' for any old DOS1 disks you might still use from time to time.
BiFi
msx guru
Posts: 3142
Posted: September 16 2006, 00:12   
Go here and download FIXBOOT.LZH

Because of a bug in FDISK310 that doesn't make the Volume ID a standard MSX-DOS2 one, that error is generated. Run FIXBOOT on your partitions... It also re-enables you to use the useful UNDEL command on it without any problems and keep the rest of the bootsector unchanged, for PC exchange purposes. SET EXPERT ON doesn't re-enable the UNDEL command.
Yukio
msx professional
Posts: 819
Posted: September 16 2006, 19:26   
Quote:

I think this question deserves a place in the Ultimate MSX FAQ!


Agree ...
You should put this into the FAQ!
manuel
msx guru
Posts: 3449
Posted: September 16 2006, 19:47   
Can someone write the complete final entry? Would make the threshold a bit lower to put it on the FAQ.
manuel
msx guru
Posts: 3449
Posted: September 17 2006, 01:17   
FAQ entry added, thanks to t00b.
MisterT
msx novice
Posts: 29
Posted: September 18 2006, 22:57   
Thanks ALL for the input

Especially mars2000you and BiFI both options worked
perfect, but i used the fixed boot, so i know the bootsector
is dos2 compatible more comforting thought....

Greetz MisterT

 
 







(c) 1994 - 2008 MSX Resource Center Foundation. MSX is a trademark of MSX Licensing Corporation.